From: Hariharan K <quic_harihk@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>
Cc: <quic_srichara@quicinc.com>, <quic_sjaganat@quicinc.com>,
<quic_kathirav@quicinc.com>, <quic_arajkuma@quicinc.com>,
<quic_anusha@quicinc.com>
Subject: Re: [PATCH 0/2] Add initial support for RDP404 of IPQ5018 family
Date: Thu, 20 Jul 2023 16:44:11 +0530 [thread overview]
Message-ID: <82a771a7-bebd-32dc-308d-a88fae002972@quicinc.com> (raw)
In-Reply-To: <5fdfe7b2-0afb-f7a1-c29a-4a7884ff8f1c@linaro.org>
On 7/20/2023 2:28 PM, Krzysztof Kozlowski wrote:
> On 20/07/2023 09:43, Hariharan K wrote:
>> Add the initial device tree support for the Reference Design
>> Platform(RDP) 404 based on IPQ5018 family of SoC. This patch
>> carries the support for Console UART and eMMC.
>>
>> This series is based on the below series,
>> https://lore.kernel.org/lkml/20230720072938.315
>> 46-1-quic_harihk@quicinc.com/
>
> Nope. You make it very difficult for us to review and follow your
> submissions. Especially considering issues in the old ipq5018 submission.
>
Sorry, will address these issues in v2.
Best regards,
Hariharan K
> Best regards,
> Krzysztof
>
prev parent reply other threads:[~2023-07-20 11:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 7:43 Hariharan K
2023-07-20 7:43 ` [PATCH 1/2] dt-bindings: arm: qcom: Document MP03.1-C2 board based on " Hariharan K
2023-07-20 7:43 ` [PATCH 2/2] arm64: dts: qcom: ipq5018: add support for the RDP404 variant Hariharan K
2023-07-20 8:12 ` [PATCH 0/2] Add initial support for RDP404 of IPQ5018 family Konrad Dybcio
2023-07-20 8:15 ` Konrad Dybcio
2023-07-20 8:59 ` Krzysztof Kozlowski
2023-07-20 8:58 ` Krzysztof Kozlowski
2023-07-20 11:14 ` Hariharan K [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=82a771a7-bebd-32dc-308d-a88fae002972@quicinc.com \
--to=quic_harihk@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=quic_anusha@quicinc.com \
--cc=quic_arajkuma@quicinc.com \
--cc=quic_kathirav@quicinc.com \
--cc=quic_sjaganat@quicinc.com \
--cc=quic_srichara@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
all inboxes | Powered by JetHome®