From: Guenter Roeck <linux@roeck-us.net>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: Jean Delvare <jdelvare@suse.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>,
Frank Li <Frank.Li@nxp.com>,
Jim Wright <wrightj@linux.vnet.ibm.com>,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] dt-bindings: hwmon: maxim,max20730: Add maxim,max20710 compatible
Date: Wed, 16 Jul 2025 07:43:36 -0700 [thread overview]
Message-ID: <06b7a7d0-53ff-4f3e-8497-152fd84e6470@roeck-us.net> (raw)
In-Reply-To: <20250701-dt-hwmon-compatibles-v1-4-ad99e65cf11b@kernel.org>
On Tue, Jul 01, 2025 at 04:00:43PM -0500, Rob Herring (Arm) wrote:
> The maxim,max20710 compatible is already in use. Add it to the
> maxim,max20730 binding as the device appears to be similar.
>
> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
Applied.
Thanks,
Guenter
next prev parent reply other threads:[~2025-07-16 14:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 21:00 [PATCH 0/6] dt-bindings: hwmon: Add undocumented compatibles Rob Herring (Arm)
2025-07-01 21:00 ` [PATCH 1/6] dt-bindings: hwmon: national,lm90: Add missing Dallas max6654 and onsemi nct72, nct214, and nct218 Rob Herring (Arm)
2025-07-01 21:00 ` [PATCH 2/6] dt-bindings: hwmon: ti,lm87: Add adi,adm1024 compatible Rob Herring (Arm)
2025-07-16 14:41 ` Guenter Roeck
2025-07-01 21:00 ` [PATCH 3/6] dt-bindings: hwmon: lltc,ltc2978: Add lltc,ltc713 compatible Rob Herring (Arm)
2025-07-16 14:42 ` Guenter Roeck
2025-07-01 21:00 ` [PATCH 4/6] dt-bindings: hwmon: maxim,max20730: Add maxim,max20710 compatible Rob Herring (Arm)
2025-07-16 14:43 ` Guenter Roeck [this message]
2025-07-01 21:00 ` [PATCH 5/6] dt-bindings: hwmon: pmbus: ti,ucd90320: Add missing compatibles Rob Herring (Arm)
2025-07-16 14:44 ` Guenter Roeck
2025-07-01 21:00 ` [PATCH 6/6] dt-bindings: trivial-devices: Add undocumented hwmon devices Rob Herring (Arm)
2025-07-16 14:45 ` 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=06b7a7d0-53ff-4f3e-8497-152fd84e6470@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=wrightj@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).