From: Conor Dooley <conor@kernel.org>
To: Wenliang <wenliang202407@163.com>
Cc: linux@roeck-us.net, jdelvare@suse.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH linux dev-6.11 2/2] dt-bindings: modified ina2xx to match SY24655(SQ52205)
Date: Wed, 11 Sep 2024 18:49:38 +0100 [thread overview]
Message-ID: <20240911-cahoots-wildland-0ea4d25d8cd8@spud> (raw)
In-Reply-To: <20240911122518.41393-2-wenliang202407@163.com>
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
On Wed, Sep 11, 2024 at 08:25:18AM -0400, Wenliang wrote:
> Modified the binding of ina2xx to make it compatible with SY24655.
Rather, you should explain why the sy24655 is compatible with the ina2xx
devices.
>
> Signed-off-by: Wenliang <wenliang202407@163.com>
> ---
> Documentation/devicetree/bindings/hwmon/ti,ina2xx.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/hwmon/ti,ina2xx.yaml b/Documentation/devicetree/bindings/hwmon/ti,ina2xx.yaml
> index 6ae961732e6b..400e7cefad17 100644
> --- a/Documentation/devicetree/bindings/hwmon/ti,ina2xx.yaml
> +++ b/Documentation/devicetree/bindings/hwmon/ti,ina2xx.yaml
> @@ -29,6 +29,7 @@ properties:
> - ti,ina237
> - ti,ina238
> - ti,ina260
> + - silergy,sy24655
Please add this in alphabetical order.
Thanks,
Conor.
>
> reg:
> maxItems: 1
> --
> 2.17.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-09-11 17:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <935f564b-fa3e-4cdf-bf12-19b897369a07@roeck-us.net>
2024-08-22 7:44 ` [PATCH linux dev 6.11] hwmon:add new hwmon driver sq52205 Wenliang
2024-08-25 22:50 ` Guenter Roeck
2024-08-30 16:08 ` Guenter Roeck
2024-09-11 12:25 ` [PATCH linux dev-6.11 1/2] hwmon: modified ina2xx to match SY24655(SQ52205) Wenliang
2024-09-11 12:25 ` [PATCH linux dev-6.11 2/2] dt-bindings: " Wenliang
2024-09-11 17:49 ` Conor Dooley [this message]
2024-10-08 12:35 ` Krzysztof Kozlowski
2024-10-08 16:26 ` Conor Dooley
[not found] ` <6dcf956c.c4f1.1926bff1453.Coremail.wenliang202407@163.com>
2024-10-08 16:17 ` Conor Dooley
2024-09-11 15:15 ` [PATCH linux dev-6.11 1/2] hwmon: " Guenter Roeck
2024-10-12 7:06 ` [PATCH linux dev-6.11 1/2] v3: hwmon: modified ina2xx to match SY24655 Wenliang
2024-10-12 7:06 ` [PATCH linux dev-6.11 2/2] v3: dt-bindings: " Wenliang
2024-10-12 10:06 ` Krzysztof Kozlowski
2024-10-12 12:12 ` Guenter Roeck
2024-09-11 17:04 ` [PATCH linux dev-6.11 1/2] hwmon: modified ina2xx to match SY24655(SQ52205) Christophe JAILLET
[not found] ` <28adb212.c4f4.1926bff2cf0.Coremail.wenliang202407@163.com>
2024-10-08 16:37 ` [PATCH linux dev-6.11 1/2] v3: hwmon: modified ina2xx to match SY24655 Guenter Roeck
2024-08-26 8:28 ` [PATCH linux dev 6.11] hwmon:add new hwmon driver sq52205 kernel test robot
2024-08-26 16:46 ` kernel test robot
2024-09-13 5:29 ` kernel test robot
2024-09-13 23:49 ` kernel test robot
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=20240911-cahoots-wildland-0ea4d25d8cd8@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@kernel.org \
--cc=wenliang202407@163.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