Patchwork Acked-by question

Patchwork Acked-by question

[Jeff Johnson]

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

Re: Patchwork Acked-by question

[Jakub Kicinski]

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..