Re: [PATCH v3 2/2] hwmon: (pmbus/vt7505) Add driver for Analog Devices MAX16545/MAX16550 and Volterra VT7505

["Pradhan, Sanman" <sanman.pradhan@hpe.com>]

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.

Thank you.

Regards,
Sanman Pradhan