mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Christopher de Guzman <christopher.deguzman@analog.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 4/4] hwmon: ltc2978: Remove LT7170 and LT7171 from curr1 iin documentation
Date: Tue, 17 Nov 2026 10:44:32 -0800	[thread overview]
Message-ID: <548a8b85-e12f-457d-93ed-86475ac7938d@roeck-us.net> (raw)
In-Reply-To: <20261110-upstream-lt7175-lt7176p-v2-4-dd60d28383bf@analog.com>

On Tue, Nov 10, 2026 at 06:00:43PM +0800, Christopher de Guzman wrote:
> LT7170 and LT7171 do not set PMBUS_HAVE_IIN, so curr1 reports the
> output current ("iout1") rather than the input current. Remove them
> from the list of chips with an "iin" curr1_label.
> 
> Signed-off-by: Christopher de Guzman <christopher.deguzman@analog.com>

Applied.

Thanks,
Guenter

      reply	other threads:[~2026-11-17 18:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10 10:00 [PATCH v2 0/4] hwmon: (pmbus/ltc2978) Add support for LT7175 and LT7176P Christopher de Guzman
2026-11-10 10:00 ` [PATCH v2 1/4] dt-bindings: hwmon: ltc2978: " Christopher de Guzman
2026-11-11 12:05   ` Krzysztof Kozlowski
2026-11-17 18:41   ` Guenter Roeck
2026-11-10 10:00 ` [PATCH v2 2/4] hwmon: (pmbus/ltc2978) " Christopher de Guzman
2026-11-17 18:42   ` Guenter Roeck
2026-11-10 10:00 ` [PATCH v2 3/4] hwmon: ltc2978: Document LT7175 and LT7176P support Christopher de Guzman
2026-11-17 18:43   ` Guenter Roeck
2026-11-10 10:00 ` [PATCH v2 4/4] hwmon: ltc2978: Remove LT7170 and LT7171 from curr1 iin documentation Christopher de Guzman
2026-11-17 18:44   ` Guenter Roeck [this message]

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=548a8b85-e12f-457d-93ed-86475ac7938d@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=Frank.Li@nxp.com \
    --cc=christopher.deguzman@analog.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=rdunlap@infradead.org \
    --cc=robh@kernel.org \
    --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®