From: "Pradhan, Sanman" <sanman.pradhan@hpe.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Jonathan Corbet <corbet@lwn.net>, Rob Herring <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.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>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Sanman Pradhan <psanman@juniper.net>
Subject: Re: [PATCH v2 1/3] hwmon: (pmbus/tps53679) Fix TPS53676 phase page decoding
Date: Wed, 16 Sep 2026 17:46:19 +0000 [thread overview]
Message-ID: <20260916174553.643587-1-sanman.pradhan@hpe.com> (raw)
In-Reply-To: <c0a3c877-eeab-4cff-ab2a-bb567f0dc3d1@roeck-us.net>
From: Sanman Pradhan <psanman@juniper.net>
Thank you for reviewing and applying the patches.
I think tps536c7_identify() has the same single-page PAGE
issue you pointed out for tps53676.
I already have a C7 patch that selects page 0 for single-page parts. I
can send it on top of your tps53676 fix so the two stay consistent, or
fold it into that fix if you prefer.
Thank you.
Regards,
Sanman Pradhan
next prev parent reply other threads:[~2026-09-16 17:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 16:48 [PATCH v2 0/3] hwmon: (pmbus/tps53679) Add TPS536C7 Pradhan, Sanman
2026-09-15 16:48 ` [PATCH v2 1/3] hwmon: (pmbus/tps53679) Fix TPS53676 phase page decoding Pradhan, Sanman
2026-09-15 16:53 ` sashiko-bot
2026-09-15 17:31 ` Guenter Roeck
2026-09-16 14:56 ` Guenter Roeck
2026-09-16 17:46 ` Pradhan, Sanman [this message]
2026-09-16 17:59 ` Guenter Roeck
2026-09-16 18:44 ` Pradhan, Sanman
2026-09-15 16:48 ` [PATCH v2 2/3] dt-bindings: trivial-devices: Add TI TPS536C7 Pradhan, Sanman
2026-09-15 16:52 ` sashiko-bot
2026-09-16 14:57 ` Guenter Roeck
2026-09-15 16:48 ` [PATCH v2 3/3] hwmon: (pmbus/tps53679) Add support for TPS536C7 Pradhan, Sanman
2026-09-15 16:57 ` sashiko-bot
2026-09-16 14:59 ` Guenter Roeck
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=20260916174553.643587-1-sanman.pradhan@hpe.com \
--to=sanman.pradhan@hpe.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=psanman@juniper.net \
--cc=robh@kernel.org \
--cc=stable@vger.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