From: Guenter Roeck <linux@roeck-us.net>
To: "Pradhan, Sanman" <sanman.pradhan@hpe.com>
Cc: "linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"krzk@kernel.org" <krzk@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"corbet@lwn.net" <corbet@lwn.net>,
"skhan@linuxfoundation.org" <skhan@linuxfoundation.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sanman Pradhan <psanman@juniper.net>,
Debjit Ghosh <dghosh@juniper.net>,
Jawahar Balaji Thirumalaisamy <jawaharb@juniper.net>,
Santhanakrishnan Balraj <sbalraj@juniper.net>,
Brian Mak <makb@juniper.net>
Subject: Re: [PATCH v3 2/2] hwmon: (pmbus/vt7505) Add driver for Analog Devices MAX16545/MAX16550 and Volterra VT7505
Date: Fri, 24 Jul 2026 14:25:31 -0700 [thread overview]
Message-ID: <f826634e-5613-4368-b23b-fabcdf2830f9@roeck-us.net> (raw)
In-Reply-To: <20260724194229.261194-1-sanman.pradhan@hpe.com>
On 7/24/26 12:42, Pradhan, Sanman wrote:
> From: Sanman Pradhan <psanman@juniper.net>
>
> On Fri, Jul 24, 2026 at 10:53:36 -0700, Guenter Roeck wrote:
>> I get delivery errors for the following addresses.
>> ddevineni@juniper.net
>> gvlaev@juniper.net
>> avadhutn@juniper.net
>>
>> meaning they are quite obviously _not_ involved in the patch approval
>> path. Please drop those addresses. Also, per
>> Documentation/process/submitting-patches.rst:
>>
>> Any further SoBs (Signed-off-by:'s) following the author's SoB are
>> from people handling and transporting the patch, but were not
>> involved in its development. SoB chains should reflect the **real**
>> route a patch took as it was propagated to the maintainers and
>> ultimately to Linus, with the first SoB entry signalling primary
>> authorship of a single author.
>>
>> Does the above SoB sequence really reflect the approval patch for this
>> patch ?
>
> Thank you for the review.
>
> Just to clarify the sign-off history, this driver consolidates work
> from several internal commits developed by multiple contributors over a
> number of years. Each Signed-off-by line was carried over from the
> contributor's original commit, where they signed off on their own work
> I did not add any sign-offs on their behalf.
>
> The contributions were roughly as follows:
>
> * Georgi Vlaev: original driver
> * Dhruva Devineni: MAX16550 support
> * Debjit Ghosh: MAX16545 support and device-specific data
> * Santhanakrishnan Balraj: severe-OCP filter
> * Avadhut Naik and JawaharBalaji Thirumalaisamy: device-tree probing
> * Brian Mak: fixes
>
> Some of these contributors have since left the company, so their
> juniper.net addresses now bounce. I've removed those addresses from
> the recipient list to avoid further delivery errors.
>
> My intention in retaining the Co-developed-by and Signed-off-by lines
> was to preserve the original authorship and sign-off history. However,
> I'm happy to adjust the attribution chain if there is a preferred way
> to handle contributors whose email addresses are no longer active.
>
Please only keep the Co-developed-by: lines, as per the guidance above.
Thanks,
Guenter
next prev parent reply other threads:[~2026-07-24 21:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 16:49 [PATCH v3 0/2] hwmon: (pmbus) Add Analog Devices MAX16545/MAX16550 and Volterra VT7505 driver Pradhan, Sanman
2026-07-24 16:49 ` [PATCH v3 1/2] dt-bindings: hwmon: pmbus: Add Analog Devices MAX16545/MAX16550 and Volterra VT7505 Pradhan, Sanman
2026-07-24 16:50 ` [PATCH v3 2/2] hwmon: (pmbus/vt7505) Add driver for " Pradhan, Sanman
2026-07-24 17:27 ` Guenter Roeck
2026-07-24 17:53 ` Guenter Roeck
2026-07-24 19:42 ` Pradhan, Sanman
2026-07-24 21:25 ` Guenter Roeck [this message]
2026-07-24 19:59 ` Pradhan, Sanman
2026-07-24 21:26 ` Guenter Roeck
2026-07-25 21:21 ` Pradhan, Sanman
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=f826634e-5613-4368-b23b-fabcdf2830f9@roeck-us.net \
--to=linux@roeck-us.net \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dghosh@juniper.net \
--cc=jawaharb@juniper.net \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=makb@juniper.net \
--cc=psanman@juniper.net \
--cc=robh@kernel.org \
--cc=sanman.pradhan@hpe.com \
--cc=sbalraj@juniper.net \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®