public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Andrei Lalaev <andrey.lalaev@gmail.com>
Cc: jdelvare@suse.com, linux@roeck-us.net, conor+dt@kernel.org,
	robh@kernel.org, christophe.jaillet@wanadoo.fr,
	linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: hwmon: Add description for sensor HTU31
Date: Mon, 27 Jan 2025 20:39:51 +0100	[thread overview]
Message-ID: <7d598b2c-dbef-4574-b154-cfef9b4c2099@kernel.org> (raw)
In-Reply-To: <57e08fc1-a319-4778-ba4a-28655f413511@gmail.com>

On 27/01/2025 20:21, Andrei Lalaev wrote:
> On 27.01.2025 08:07, Krzysztof Kozlowski wrote:
>> On Sun, Jan 26, 2025 at 03:40:56PM +0100, Andrei Lalaev wrote:
>>> Add trivial binding for HTU31 Temperature and Humidity sensor.
>>>
>>> Signed-off-by: Andrei Lalaev <andrey.lalaev@gmail.com>
>>> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>> ---
>>>  Documentation/devicetree/bindings/trivial-devices.yaml | 2 ++
>>>  1 file changed, 2 insertions(+)
>>>
>>
>> Please version your patchsets correctly. `git format-patch -v2` or b4.
>>
>> This is not v1 and you could not get my ack on v1.
>>
> 
> Oh, my bad, sorry, I manually edited the cover letter and forgot about patches' subjects :/
> 
> Should I resend v2 with normal versioning, or would you prefer me to go straight to v3?

Tools might work fine with it, so no need to resend, unless Guenter
asks. But if you send v3 for any reason, be sure to mark all of the patches.

Best regards,
Krzysztof

  reply	other threads:[~2025-01-27 19:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-26 14:40 [PATCH v2 0/2] Add driver for HTU31 Andrei Lalaev
2025-01-26 14:40 ` [PATCH 1/2] hwmon: add " Andrei Lalaev
2025-01-26 14:59   ` Guenter Roeck
2025-01-26 19:16     ` Andrei Lalaev
2025-01-26 19:36       ` Guenter Roeck
2025-01-26 14:40 ` [PATCH 2/2] dt-bindings: hwmon: Add description for sensor HTU31 Andrei Lalaev
2025-01-27  7:07   ` Krzysztof Kozlowski
2025-01-27 19:21     ` Andrei Lalaev
2025-01-27 19:39       ` Krzysztof Kozlowski [this message]
2025-01-27 20:14         ` Guenter Roeck
  -- strict thread matches above, loose matches on Subject: below --
2025-01-23 20:25 [PATCH 0/2] Add driver for HTU31 Andrei Lalaev
2025-01-23 20:25 ` [PATCH 2/2] dt-bindings: hwmon: Add description for sensor HTU31 Andrei Lalaev
2025-01-24  8:26   ` 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=7d598b2c-dbef-4574-b154-cfef9b4c2099@kernel.org \
    --to=krzk@kernel.org \
    --cc=andrey.lalaev@gmail.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@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