From: Marek Vasut <marex@nabladev.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-pm@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
Flaviu Nistor <flaviu.nistor@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: hwmon: tmp102: Fix up TMP103 bindings
Date: Tue, 1 Sep 2026 20:30:14 +0200 [thread overview]
Message-ID: <cad5d9ee-401d-456a-a27f-31038fbae939@nabladev.com> (raw)
In-Reply-To: <0a4ed80d-a5c0-4b5b-b41d-76c37adb99bd@roeck-us.net>
On 9/1/26 8:17 PM, Guenter Roeck wrote:
> On Tue, Sep 01, 2026 at 07:47:54PM +0200, Marek Vasut wrote:
>> The TMP102 and TMP110 are backward compatible, therefore the valid
>> compatible strings are "ti,tmp110", "ti,tmp102" and "ti,tmp102" .
>>
>> The TMP103 is not backward compatible with TMP102, but it does share a
>> schema now, therefore the only valid compatible string for the TMP103
>> should be "ti,tmp103" .
>>
>> Make exactly those three compatible strings valid and everything else
>> rejected.
>>
>> Fixes: d67ec24d3f07 ("dt-bindings: hwmon: tmp102: move ti,tmp103 out of trivial-devices.yaml")
>> Signed-off-by: Marek Vasut <marex@nabladev.com>
>> Acked-by: Conor Dooley <conor.dooley@microchip.com>
>
> Applied (I'll squash it with d67ec24d3f07).
Thank you
prev parent reply other threads:[~2026-09-01 18:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 17:47 [PATCH v3 1/2] dt-bindings: hwmon: tmp102: Fix up TMP103 bindings Marek Vasut
2026-09-01 17:47 ` [PATCH v3 2/2] dt-bindings: hwmon: tmp102: Document TMP113 Marek Vasut
2026-09-01 17:53 ` sashiko-bot
2026-09-01 18:03 ` Conor Dooley
2026-09-01 18:20 ` Guenter Roeck
2026-09-01 17:53 ` [PATCH v3 1/2] dt-bindings: hwmon: tmp102: Fix up TMP103 bindings sashiko-bot
2026-09-01 18:03 ` Conor Dooley
2026-09-01 18:17 ` Guenter Roeck
2026-09-01 18:30 ` Marek Vasut [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=cad5d9ee-401d-456a-a27f-31038fbae939@nabladev.com \
--to=marex@nabladev.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=flaviu.nistor@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@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