From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Komal Bajaj <quic_kbajaj@quicinc.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.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 v4 1/3] dt-bindings: arm: qcom: Add QCM6490 IDP and QCS6490 RB3Gen2 board
Date: Fri, 17 Nov 2023 14:04:33 +0100 [thread overview]
Message-ID: <b05edb57-35de-4e84-bdd6-b64d67164d91@linaro.org> (raw)
In-Reply-To: <20231117125056.32503-2-quic_kbajaj@quicinc.com>
On 17/11/2023 13:50, Komal Bajaj wrote:
> Document the qcom,qcm6490-idp and qcs6490-rb3gen2 boards.
> qcm6490-idp based off qcm6490 SoC derived from sc7280 meant for
> various form factor including IoT and qcs6490-rb3gen2 based off
> qcs6490 SoC derivative of qcm6490 without internal modem.
>
> Co-developed by: Naina Mehta <quic_nainmeht@quicinc.com>
> Signed-off by: Naina Mehta <quic_nainmeht@quicinc.com>
> Signed-off-by: Komal Bajaj <quic_kbajaj@quicinc.com>
> ---
> Documentation/devicetree/bindings/arm/qcom.yaml | 2 ++
You must explain why you dropped the Reviewed-by tag.
There is nothing in the changelog explaining it.
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-11-17 13:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 12:50 [PATCH v4 0/3] Add support for qcm6490 idp and qcs6490 rb3gen2 board Komal Bajaj
2023-11-17 12:50 ` [PATCH v4 1/3] dt-bindings: arm: qcom: Add QCM6490 IDP and QCS6490 RB3Gen2 board Komal Bajaj
2023-11-17 13:04 ` Krzysztof Kozlowski [this message]
2023-11-17 12:50 ` [PATCH v4 2/3] arm64: dts: qcom: Add base qcm6490 idp board dts Komal Bajaj
2023-11-18 1:11 ` Konrad Dybcio
2023-11-17 12:50 ` [PATCH v4 3/3] arm64: dts: qcom: Add base qcs6490-rb3gen2 " Komal Bajaj
2023-11-18 1:11 ` Konrad Dybcio
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=b05edb57-35de-4e84-bdd6-b64d67164d91@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_kbajaj@quicinc.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).