From: Jakub Kicinski <kuba@kernel.org>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: <workflows@vger.kernel.org>, Kalle Valo <kvalo@kernel.org>
Subject: Re: Patchwork Acked-by question
Date: Mon, 22 Jan 2024 13:07:56 -0800 [thread overview]
Message-ID: <20240122130756.1b33f257@kernel.org> (raw)
In-Reply-To: <403a40ac-10f1-46d9-bab4-86cd713fe5da@quicinc.com>
On Mon, 22 Jan 2024 12:10:39 -0800 Jeff Johnson wrote:
> I co-maintain the ath1*k wireless drivers with Kalle. Our current
> workflow is that I review and give an Acked-by and then Kalle does the
> actual patch integration.
>
> My observation is that when I give an Acked-by mailing list comments on
> individual patches, the appropriate flag is set in patchwork. However,
> this does not seem to work for a series of patches if I tag just the
> cover letter. Just curious if I'm doing something wrong, or if I'm
> expected to tag each individual patch, or if this is a missing
> project-specific configuration?
This is a long standing limitation:
https://github.com/getpatchwork/patchwork/issues/113
There's quite a few annoyances with patchwork, so people end up
scripting around it (netdev+bpf maintainers use
https://git.kernel.org/pub/scm/linux/kernel/git/dborkman/pw.git/ )
or using b4..
prev parent reply other threads:[~2024-01-22 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 20:10 Patchwork Acked-by question Jeff Johnson
2024-01-22 21:07 ` Jakub Kicinski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240122130756.1b33f257@kernel.org \
--to=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=quic_jjohnson@quicinc.com \
--cc=workflows@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).