From: Krzysztof Kozlowski <krzk@kernel.org>
To: arthur.becker@sentec.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>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/2] dt-bindings: iio: light: add VEML6040 RGBW-LS bindings
Date: Tue, 4 Jun 2024 10:45:00 +0200 [thread overview]
Message-ID: <e740deb8-e412-4913-9a79-59ad8e117d53@kernel.org> (raw)
In-Reply-To: <20240604-veml6040-v4-2-5a4d59597874@sentec.com>
On 04/06/2024 10:01, Arthur Becker via B4 Relay wrote:
> From: Arthur Becker <arthur.becker@sentec.com>
>
> Device tree bindings for the vishay VEML6040 RGBW light sensor iio
> driver
>
> Signed-off-by: Arthur Becker <arthur.becker@sentec.com>
> ---
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
If there is any resend:
A nit, subject: drop second/last, redundant "bindings". The
"dt-bindings" prefix is already stating that these are bindings.
See also:
https://elixir.bootlin.com/linux/v6.7-rc8/source/Documentation/devicetree/bindings/submitting-patches.rst#L18
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-06-04 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 8:01 [PATCH v4 0/2] Add driver for Vishay VEML6040 Arthur Becker via B4 Relay
2024-06-04 8:01 ` [PATCH v4 1/2] iio: light: " Arthur Becker via B4 Relay
2024-06-04 8:01 ` [PATCH v4 2/2] dt-bindings: iio: light: add VEML6040 RGBW-LS bindings Arthur Becker via B4 Relay
2024-06-04 8:45 ` Krzysztof Kozlowski [this message]
2024-06-04 8:59 ` [EXTERNAL]Re: " Arthur Becker
2024-06-04 9:05 ` Krzysztof Kozlowski
2024-06-09 8:53 ` Jonathan Cameron
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=e740deb8-e412-4913-9a79-59ad8e117d53@kernel.org \
--to=krzk@kernel.org \
--cc=arthur.becker@sentec.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=javier.carrasco.cruz@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