mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sridharan S N <quic_sridsn@quicinc.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	<agross@kernel.org>, <andersson@kernel.org>,
	<konrad.dybcio@linaro.org>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
	<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] arm64: dts: qcom: ipq9574: add support for the RDP417 variant
Date: Thu, 13 Jul 2023 17:37:09 +0530	[thread overview]
Message-ID: <946b3761-a280-b0b6-e3ac-860d68f7072a@quicinc.com> (raw)
In-Reply-To: <f9bfb051-aa39-0e87-6597-e5b5ce85a37f@linaro.org>


On 7/13/2023 5:28 PM, Krzysztof Kozlowski wrote:
> On 13/07/2023 13:55, Sridharan S N wrote:
>> Add the initial device tree support for the Reference Design
>> Platform(RDP) 417 based on IPQ9574 family of SoC.
>>
>> This patch depends on below patchset:
>> https://lore.kernel.org/lkml/20230713105909.14209-2-quic_anusha@quicinc.com/
> This does not make sense in commit log. Why would you store it in commit
> in the first place? Please put dependencies with changelog, so after ---
> separator.
>
> Best regards,
> Krzysztof

Sorry,I overlooked it. Will move the dependencies to change log and post v2


Thanks,

Sridharan

>

      reply	other threads:[~2023-07-13 12:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13 11:55 [PATCH 0/2] Add initial support for RDP417 of IPQ9574 family Sridharan S N
2023-07-13 11:55 ` [PATCH 1/2] dt-bindings: arm: qcom: document AL01-C1 board based on " Sridharan S N
2023-07-13 11:57   ` Krzysztof Kozlowski
2023-07-13 11:55 ` [PATCH 2/2] arm64: dts: qcom: ipq9574: add support for the RDP417 variant Sridharan S N
2023-07-13 11:58   ` Krzysztof Kozlowski
2023-07-13 12:07     ` Sridharan S N [this message]

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=946b3761-a280-b0b6-e3ac-860d68f7072a@quicinc.com \
    --to=quic_sridsn@quicinc.com \
    --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=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®