[PATCH 0/2] md: Replace snprintf with scnprintf

Cory Todd cory.todd at canonical.com
Wed Oct 19 14:09:39 UTC 2022


On Wed, Oct 19, 2022 at 10:08:09AM +0200, Stefan Bader wrote:
> In my joyful morning mood I am tempted to NACK this for formal reasons. Why
> does the cover email not contain any indication where it should go to? Why
> do the patches invent yet another way to define where they apply to?
> 
> Andrea, Cory,
> 
> that would be a question which you could ask. Ideally (and I thought that
> was what is documented) this should have looked like:
> 
> [SRU K/J/F][PATCH 0/1] ...
> - [SRU K][PATCH 1/1] ...
> - [SRU J/F][PATCH 1/1] ...
> 
> If that was not for the primary kernel (or if one wants to be explicit) it
> should be more like the handle format, so "K:linux" or "J/F:linux". There is
> already use of source names without series mixed with series which is a bit
> of a pain to read.
> 

Understood, thanks for the correction and yes I do see that is
documented. I'll keep a closer eye on this in the future.

I agree that a checker tool would be nice for this.

- corytodd

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/kernel-team/attachments/20221019/7763812d/attachment.sig>


More information about the kernel-team mailing list