[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cc5f7e49-5df2-4f1d-93db-4a5b045ddfad@kernel.org>
Date: Tue, 7 Oct 2025 16:22:12 +0900
From: Krzysztof Kozlowski <krzk@...nel.org>
To: remi.buisson@....com, Jonathan Cameron <jic23@...nel.org>,
David Lechner <dlechner@...libre.com>, Nuno Sá
<nuno.sa@...log.com>, Andy Shevchenko <andy@...nel.org>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>
Cc: linux-kernel@...r.kernel.org, linux-iio@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH v7 1/9] dt-bindings: iio: imu: Add inv_icm45600
On 07/10/2025 16:20, Remi Buisson via B4 Relay wrote:
> From: Remi Buisson <remi.buisson@....com>
>
> Document the ICM-45600 devices devicetree bindings.
> Specific variants of the device are defined because of their
> differences in terms of FSR or advanced features like eDMP.
<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
Powered by blists - more mailing lists