From: Krzysztof Kozlowski <krzk@kernel.org>
To: Umang Chheda <umang.chheda@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 1/2] dt-bindings: arm: qcom: Add bindings for Monaco EVK
Date: Sat, 2 Aug 2025 09:46:46 +0200 [thread overview]
Message-ID: <267b2d6c-468d-4bff-ac06-c6755706a398@kernel.org> (raw)
In-Reply-To: <20250801163607.1464037-2-umang.chheda@oss.qualcomm.com>
On 01/08/2025 18:36, Umang Chheda wrote:
> From: Umang Chheda <uchheda.chheda@oss.qualcomm.com>
>
> Introduce new bindings for the Monaco Evaluation Kit (EVK),
> an IoT board based on the QCS8300 SoC.
>
> Signed-off-by: Umang Chheda <umang.chheda@oss.qualcomm.com>
> ---
> Documentation/devicetree/bindings/arm/qcom.yaml | 1 +
> 1 file changed, 1 insertion(+)
This is v2, so where is any changelog?
A nit, subject: drop second/last, redundant "bindings for". 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:[~2025-08-02 7:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 16:36 [PATCH V2 0/2] Introduce initial support for Monaco Evaluation Kit Umang Chheda
2025-08-01 16:36 ` [PATCH V2 1/2] dt-bindings: arm: qcom: Add bindings for Monaco EVK Umang Chheda
2025-08-02 7:46 ` Krzysztof Kozlowski [this message]
2025-08-04 18:22 ` Umang Chheda
2025-08-01 16:36 ` [PATCH V2 2/2] arm64: dts: qcom: Add Monaco evaluation kit initial board support Umang Chheda
2025-08-01 17:14 ` Dmitry Baryshkov
2025-08-04 18:18 ` Umang Chheda
2025-08-05 12:52 ` Konrad Dybcio
2025-08-02 7:49 ` [PATCH V2 0/2] Introduce initial support for Monaco Evaluation Kit Krzysztof Kozlowski
2025-08-04 18:23 ` Umang Chheda
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=267b2d6c-468d-4bff-ac06-c6755706a398@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=umang.chheda@oss.qualcomm.com \
/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