public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: gomba007@gmail.com, Jonathan Cameron <jic23@kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Add support for the DFRobot SEN0322 oxygen sensor
Date: Tue, 6 May 2025 11:00:15 +0200	[thread overview]
Message-ID: <4ef1f428-d580-4263-9190-d187d1fd0e53@kernel.org> (raw)
In-Reply-To: <20250506-iio-chemical-sen0322-v3-0-d6aa4acd00e0@gmail.com>

On 06/05/2025 10:53, Tóth János via B4 Relay wrote:
> This patchset adds a driver and the documentation for the
> DFRobot SEN0322 oxygen sensor.
> 
> Signed-off-by: Tóth János <gomba007@gmail.com>
> ---
> Changes in v3:
> - Refactor based on reviewer's suggestions.

What exactly changed? I do not see any changes in the binding but you
decided to drop my review tag.


<form letter>
This is a friendly reminder during the review process.

It looks like you received a tag and forgot to add it.

If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new versions
of patchset, under or above your Signed-off-by tag, unless patch changed
significantly (e.g. new properties added to the DT bindings). Tag is
"received", when provided in a message replied to you on the mailing
list. Tools like b4 can help here. However, there's no need to repost
patches *only* to add the tags. The upstream maintainer will do that for
tags received on the version they apply.

Please read:
https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577

If a tag was not added on purpose, please state why and what changed.
</form letter>

Best regards,
Krzysztof

  parent reply	other threads:[~2025-05-06  9:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06  8:53 [PATCH v3 0/2] Add support for the DFRobot SEN0322 oxygen sensor Tóth János via B4 Relay
2025-05-06  8:53 ` [PATCH v3 1/2] dt-bindings: trivial-devices: Document SEN0322 Tóth János via B4 Relay
2025-05-06  8:53 ` [PATCH v3 2/2] iio: chemical: Add driver for SEN0322 Tóth János via B4 Relay
2025-05-06  9:00 ` Krzysztof Kozlowski [this message]
2025-05-06  9:03   ` [PATCH v3 0/2] Add support for the DFRobot SEN0322 oxygen sensor Tóth János

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=4ef1f428-d580-4263-9190-d187d1fd0e53@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gomba007@gmail.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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