linux-kernel - Re: [PATCH v5 02/10] locking/mutex: introduce devm_mutex

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHp75Ve_4oM7PkNsWAQZ1XEBQ8knROjdjyh17YLdSeXw7M6juA@mail.gmail.com>
Date: Tue, 12 Mar 2024 10:58:16 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Christophe Leroy <christophe.leroy@...roup.eu>
Cc: George Stark <gnstark@...utedevices.com>, "pavel@....cz" <pavel@....cz>, 
	"lee@...nel.org" <lee@...nel.org>, "vadimp@...dia.com" <vadimp@...dia.com>, 
	"mpe@...erman.id.au" <mpe@...erman.id.au>, "npiggin@...il.com" <npiggin@...il.com>, 
	"hdegoede@...hat.com" <hdegoede@...hat.com>, "mazziesaccount@...il.com" <mazziesaccount@...il.com>, 
	"peterz@...radead.org" <peterz@...radead.org>, "mingo@...hat.com" <mingo@...hat.com>, 
	"will@...nel.org" <will@...nel.org>, "longman@...hat.com" <longman@...hat.com>, 
	"boqun.feng@...il.com" <boqun.feng@...il.com>, "nikitos.tr@...il.com" <nikitos.tr@...il.com>, 
	"kabel@...nel.org" <kabel@...nel.org>, 
	"linux-leds@...r.kernel.org" <linux-leds@...r.kernel.org>, 
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, 
	"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>, 
	"kernel@...utedevices.com" <kernel@...utedevices.com>
Subject: Re: [PATCH v5 02/10] locking/mutex: introduce devm_mutex_init

On Tue, Mar 12, 2024 at 7:41 AM Christophe Leroy
<christophe.leroy@...roup.eu> wrote:
> Le 12/03/2024 à 01:01, George Stark a écrit :
> > [Vous ne recevez pas souvent de courriers de gnstark@...utedevices.com.
> > Découvrez pourquoi ceci est important à
> > https://aka.ms/LearnAboutSenderIdentification ]
> > On 3/7/24 13:34, Andy Shevchenko wrote:
> >> On Thu, Mar 7, 2024 at 4:40 AM George Stark
> >> <gnstark@...utedevices.com> wrote:

..

> >>> Signed-off-by: George Stark <gnstark@...utedevices.com>
> >>> Signed-off-by: Christophe Leroy <christophe.leroy@...roup.eu>
> >>
> >>>   Hello Christophe. Hope you don't mind I put you SoB tag because you
> >>> helped alot
> >>>   to make this patch happen.
> >>
> >> You also need to figure out who should be the author of the patch and
> >> probably add a (missing) Co-developed-by. After all you should also
> >> follow the correct order of SoBs.
> >
> > Thanks for the review.
> > I explained in the other letter as I see it. So I'd leave myself
> > as author and add appropriate tag with Christophe's name.
> > BTW what do you mean by correct SoB order?
> > Is it alphabetical order or order of importance?

> The correct order is to first have the Author's SoB.

At the last one is submitters. So, if it's the same person, which one
should go first?

-- 
With Best Regards,
Andy Shevchenko