public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Arthur Becker <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-kernel@vger.kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [EXTERNAL]Re: [PATCH v4 2/2] dt-bindings: iio: light: add VEML6040 RGBW-LS bindings
Date: Tue, 4 Jun 2024 11:05:43 +0200	[thread overview]
Message-ID: <f86a8de8-126b-4582-8fac-a5e273851cab@kernel.org> (raw)
In-Reply-To: <ZR1P278MB11171DD79D5A09580FEEF4A181F82@ZR1P278MB1117.CHEP278.PROD.OUTLOOK.COM>

On 04/06/2024 10:59, Arthur Becker wrote:
>> 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
> 
> Oups! I had read that part of the documentation but forgot about it...
> I'll think about it next time.
> 

It's fine, no worries.

Best regards,
Krzysztof


  reply	other threads:[~2024-06-04  9:05 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
2024-06-04  8:59     ` [EXTERNAL]Re: " Arthur Becker
2024-06-04  9:05       ` Krzysztof Kozlowski [this message]
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=f86a8de8-126b-4582-8fac-a5e273851cab@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