public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Fabien Proriol <fabien.proriol@viavisolutions.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Sebastian Reichel <sre@kernel.org>
Cc: Sebastian Reichel <sebastian.reichel@collabora.com>,
	fabien.proriol@kazoe.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the battery tree
Date: Mon, 8 Sep 2025 09:42:21 +0200	[thread overview]
Message-ID: <cc37b088-696f-4f91-9159-30e839b7ffb9@viavisolutions.com> (raw)
In-Reply-To: <20250908080739.5f33c79f@canb.auug.org.au>

Hi,

In fact, <fabien.proriol@viavisolutions.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@kazoe.org>).

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 ?

Thanks,

Fabien Proriol

Le 08/09/2025 à 00:07, Stephen Rothwell a écrit :
> Hi all,
>
> Commit
>
>    8543d1c462e2 ("power: supply: sbs-charger: Support multiple devices")
>
> is missing a Signed-off-by from its author.
>
> Actually the author in the commit is
>
>    fabien.proriol@kazoe.org <fabien.proriol@kazoe.org>
>
> While the SoB line is
>
>    Signed-off-by: Fabien Proriol <fabien.proriol@viavisolutions.com>
>
> We should prefer that they match.  Also we prefer full names in all
> email addresses.
>

  reply	other threads:[~2025-09-08  7:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-07 22:07 linux-next: Signed-off-by missing for commit in the battery tree Stephen Rothwell
2025-09-08  7:42 ` Fabien Proriol [this message]
2025-09-08 13:13   ` Sebastian Reichel
  -- strict thread matches above, loose matches on Subject: below --
2022-02-13 11:00 Stephen Rothwell
2019-05-01 21:52 Stephen Rothwell
2019-05-01 22:30 ` Sebastian Reichel
2018-03-12  1:40 Stephen Rothwell
     [not found] ` <CANEr7oV8GTU8X1ijUYJKZjF6Pdr1i7+mvUqoDCaaKBCPkvrFgg@mail.gmail.com>
2018-03-12  9:46   ` Pierre Bourdon (delroth)
2018-03-12 13:40     ` Sebastian Reichel

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=cc37b088-696f-4f91-9159-30e839b7ffb9@viavisolutions.com \
    --to=fabien.proriol@viavisolutions.com \
    --cc=fabien.proriol@kazoe.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sebastian.reichel@collabora.com \
    --cc=sfr@canb.auug.org.au \
    --cc=sre@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