Linux IIO development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jianping.Shen@de.bosch.com, jic23@kernel.org, lars@metafoo.de,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	dima.fedrau@gmail.com, marcelo.schmitt1@gmail.com,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Christian.Lorenz3@de.bosch.com,
	Ulrike.Frauendorf@de.bosch.com, Kai.Dolde@de.bosch.com
Subject: Re: [PATCH v3 1/2] dt-bindings: iio: imu: smi330: Add binding
Date: Fri, 4 Jul 2025 17:14:22 +0200	[thread overview]
Message-ID: <1196da81-ecd7-487c-8afc-e0d3660fa158@kernel.org> (raw)
In-Reply-To: <20250703153823.806073-2-Jianping.Shen@de.bosch.com>

On 03/07/2025 17:38, Jianping.Shen@de.bosch.com wrote:
> From: Jianping Shen <Jianping.Shen@de.bosch.com>
> 
> Add devicetree binding for Bosch imu smi330.
> The smi330 is a combined three axis angular rate and
> three axis acceleration sensor module.
> 
> Signed-off-by: Jianping Shen <Jianping.Shen@de.bosch.com>
<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

  reply	other threads:[~2025-07-04 15:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03 15:38 [PATCH v3 0/2] iio: imu: smi330: add bosch smi330 driver Jianping.Shen
2025-07-03 15:38 ` [PATCH v3 1/2] dt-bindings: iio: imu: smi330: Add binding Jianping.Shen
2025-07-04 15:14   ` Krzysztof Kozlowski [this message]
2025-07-03 15:38 ` [PATCH v3 2/2] iio: imu: smi330: Add driver Jianping.Shen
2025-07-04 14:23   ` kernel test robot
2025-07-06 16:53   ` Jonathan Cameron
2025-07-09 19:38     ` AW: " Shen Jianping (ME-SE/EAD2)
2025-07-13 13:42       ` Jonathan Cameron
2025-07-15 18:35         ` AW: " Shen Jianping (ME-SE/EAD2)
2025-07-17 14:04           ` Jonathan Cameron
2025-07-23  9:46             ` AW: " Shen Jianping (ME-SE/EAD2)
2025-07-24 15:07               ` Jonathan Cameron
2025-07-28 12:14                 ` AW: " Shen Jianping (ME-SE/EAD2)
2025-07-28 13:07                   ` Jonathan Cameron
2025-07-28 14:10                     ` AW: " Shen Jianping (ME-SE/EAD2)

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=1196da81-ecd7-487c-8afc-e0d3660fa158@kernel.org \
    --to=krzk@kernel.org \
    --cc=Christian.Lorenz3@de.bosch.com \
    --cc=Jianping.Shen@de.bosch.com \
    --cc=Kai.Dolde@de.bosch.com \
    --cc=Ulrike.Frauendorf@de.bosch.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dima.fedrau@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=marcelo.schmitt1@gmail.com \
    --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