From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: <workflows@vger.kernel.org>
Cc: Kalle Valo <kvalo@kernel.org>
Subject: Patchwork Acked-by question
Date: Mon, 22 Jan 2024 12:10:39 -0800 [thread overview]
Message-ID: <403a40ac-10f1-46d9-bab4-86cd713fe5da@quicinc.com> (raw)
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 specifically in reference to
<https://patchwork.kernel.org/project/linux-wireless/>
And where I'd hope that the following would tag every patch in the series:
<https://lore.kernel.org/linux-wireless/bbfc4752-0a54-4e8b-b5c3-86005ebaa834@quicinc.com/>
/jeff
next reply other threads:[~2024-01-22 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 20:10 Jeff Johnson [this message]
2024-01-22 21:07 ` Patchwork Acked-by question Jakub Kicinski
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=403a40ac-10f1-46d9-bab4-86cd713fe5da@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=kvalo@kernel.org \
--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).