From: Conor Dooley <conor@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Wenliang <wenliang202407@163.com>,
linux@roeck-us.net, book <book@100ask.localdomain>,
jdelvare@suse.com, linux-hwmon@vger.kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH linux dev-6.11 v3 2/2] dt-bindings: Add SY24655 to ina2xx devicetree bindings
Date: Sun, 3 Nov 2024 22:39:31 +0000 [thread overview]
Message-ID: <20241103-saloon-footsie-42dea85a903b@spud> (raw)
In-Reply-To: <b2d1e4cf-b068-4bab-9735-d9d4ff449a09@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
On Sun, Nov 03, 2024 at 05:52:59PM +0100, Krzysztof Kozlowski wrote:
> On 03/11/2024 17:46, Krzysztof Kozlowski wrote:
> > On 03/11/2024 17:39, Wenliang wrote:
> >> From: book <book@100ask.localdomain>
> >>
> >> SY24655 is similar to INA226. Its supply voltage and pin definitions
> >> are therefore the same. Compared to INA226, SY24655 has two additional
> >> registers for configuring and calculating average power.
> >>
> >> Signed-off-by: book <book@100ask.localdomain>
> >> Acked-by: Conor Dooley <conor.dooley@microchip.com>
> >
> > NAK, this never happened. If you think otherwise: provide proof, please.
>
> Hm, now I found previous v3, so ack happened, but patch still has
> incorrect author.
I didn't ack it with this weird authorship, so that needs to be fixed
before the ack can be applied.
>
> Please really carefully read submitting patches document, especially
> parts about sending new versions, changelogs, subjects.
>
>
> >
> > Nothing improved in this binding, actually it got even worse with fake
> > email and probably name as well.
>
>
> Best regards,
> Krzysztof
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-11-03 22:39 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
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 [this message]
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=20241103-saloon-footsie-42dea85a903b@spud \
--to=conor@kernel.org \
--cc=book@100ask.localdomain \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@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