From: Guenter Roeck <linux@roeck-us.net>
To: Kurt Borja <kuurtb@gmail.com>, Jean Delvare <jdelvare@suse.com>,
Jonathan Corbet <corbet@lwn.net>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-hwmon@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v3 2/4] hwmon: (sht21) Add support for SHT20, SHT25 chips
Date: Mon, 8 Sep 2025 06:31:49 -0700 [thread overview]
Message-ID: <c596e196-7e5f-4600-ada1-7c96af8c0a38@roeck-us.net> (raw)
In-Reply-To: <20250907-sht2x-v3-2-bf846bd1534b@gmail.com>
On 9/7/25 18:33, Kurt Borja wrote:
> All sht2x chips share the same communication protocol so add support for
> them.
>
> Cc: stable@vger.kernel.org
FWIW, I am going to drop this when applying. I don't add stable tags
for patches which are not bug fixes. Anyone who wants such patches
backported can request that separately after the patch is upstream.
Guenter
next prev parent reply other threads:[~2025-09-08 13:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 1:33 [PATCH v3 0/4] hwmon: (sht21) Add devicetree support Kurt Borja
2025-09-08 1:33 ` [PATCH v3 1/4] hwmon: (sht21) Documentation cleanup Kurt Borja
2025-09-08 1:33 ` [PATCH v3 2/4] hwmon: (sht21) Add support for SHT20, SHT25 chips Kurt Borja
2025-09-08 13:31 ` Guenter Roeck [this message]
2025-09-08 1:33 ` [PATCH v3 3/4] hwmon: (sht21) Add devicetree support Kurt Borja
2025-09-08 7:03 ` Krzysztof Kozlowski
2025-09-08 1:33 ` [PATCH v3 4/4] dt-bindings: trivial-devices: Add sht2x sensors Kurt Borja
2025-09-08 7:02 ` Krzysztof Kozlowski
2025-09-08 11:28 ` Kurt Borja
2025-09-08 14:16 ` Krzysztof Kozlowski
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=c596e196-7e5f-4600-ada1-7c96af8c0a38@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andriy.shevchenko@linux.intel.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=kuurtb@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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