Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Wenliang <wenliang202407@163.com>, linux@roeck-us.net
Cc: jdelvare@suse.com, linux-hwmon@vger.kernel.org,
	linux-kernel@vger.kernel.org, robh@kernel.org,
	conor+dt@kernel.org, krzk+dt@kernel.org
Subject: Re: [PATCH v3 2/2] dt-bindings: modified ina2xx to match SY24655
Date: Fri, 25 Oct 2024 09:56:20 +0200	[thread overview]
Message-ID: <554abf6f-7c34-469b-82ba-4973b3338073@kernel.org> (raw)
In-Reply-To: <20241024083055.82047-2-wenliang202407@163.com>

On 24/10/2024 10:30, Wenliang wrote:
> Adding Silergy's sy24655 as an adapter chip for Ina2xx drivers.
> 
> Because it is similar to INA226, the supply voltage and pin definitions
> are the same. It also supports IIC communication, with only two
> additional registers added for configuring and calculating average power.
> 
> Signed-off-by: Wenliang <wenliang202407@163.com>

<form letter>
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.

Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.

You missed at least devicetree list (maybe more), so this won't be
tested by automated tooling.

Please kindly resend and include all necessary To/Cc entries.
</form letter>

Best regards,
Krzysztof


  parent reply	other threads:[~2024-10-25  7:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <80bfd968-8f12-46b1-9b72-837502ccdb2a@roeck-us.ne>
2024-10-24  8:30 ` [PATCH v3 1/2] hwmon: modified ina2xx to match SY24655 Wenliang
2024-10-24  8:30   ` [PATCH v3 2/2] dt-bindings: " Wenliang
2024-10-24 16:32     ` Conor Dooley
2024-10-24 16:33       ` Conor Dooley
2024-10-24 16:55     ` Guenter Roeck
2024-10-25  7:56     ` Krzysztof Kozlowski [this message]
2024-10-24 17:10   ` [PATCH v3 1/2] hwmon: " Guenter Roeck
2024-11-03 16:39     ` [PATCH linux dev-6.11 v3 1/2] hwmon: (ina226) Add support for SY24655 Wenliang
2024-11-03 16:39       ` [PATCH linux dev-6.11 v3 2/2] dt-bindings: Add SY24655 to ina2xx devicetree bindings Wenliang
2024-11-03 16:46         ` Krzysztof Kozlowski
2024-11-03 16:52           ` Krzysztof Kozlowski
2024-11-03 22:39             ` Conor Dooley
2024-11-03 17:37       ` [PATCH linux dev-6.11 v3 1/2] hwmon: (ina226) Add support for SY24655 Guenter Roeck
2024-11-06 15:05         ` [PATCH " wenliang
2024-11-06 15:05           ` [PATCH v3 2/2] dt-bindings: Add SY24655 to ina2xx devicetree bindings wenliang
2024-11-06 15:31           ` [PATCH v3 1/2] hwmon: (ina226) Add support for SY24655 Guenter Roeck
2024-11-06 15:39           ` 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=554abf6f-7c34-469b-82ba-4973b3338073@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@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