linux-kernel - Re: linux-next: Signed-off-by missing for commit in the battery tree

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] [day] [month] [year] [list]

Message-ID: <3zg7kxnpnqcovgfdqwjmkpqyq4t7cxupmjqhsstx7fie2t2cu3@4b5d22kg7sfn>
Date: Mon, 8 Sep 2025 15:13:09 +0200
From: Sebastian Reichel <sebastian.reichel@...labora.com>
To: Fabien Proriol <fabien.proriol@...visolutions.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>, fabien.proriol@...oe.org, 
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the battery tree

Hello Fabien,

Please do not top-top :)

>Le 08/09/2025 à 00:07, Stephen Rothwell a écrit :
>> Commit
>>    8543d1c462e2 ("power: supply: sbs-charger: Support multiple devices")
>> is missing a Signed-off-by from its author.
>
> In fact, <fabien.proriol@...visolutions.com> is the email of my companies,
> unfortunately, the email server broke the indentation of my patch.
> This why I used my own personal address to re-send the same commit
> (<fabien.proriol@...oe.org>).

Actually your second patch was also broken and I had to fix it up
while applying. You should have a look at 'b4', which helps you a
lot with these kind of issues:

https://b4.docs.kernel.org/en/latest/

> For me, we can use either one without any problem, so, if you can change to
> use the same in the signed-off and the commit, it's OK for me.
> 
> How to process ? can you change it or, should I re-transmit the message
> again ?

The first patch was send by your work mail and signed off by it.
I've used that to fix things up.

Please have a look at fixing your mail setup before sending more
patches - be it with b4 or via some other setup :)

Greetings,

-- Sebastian

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)