From: Rohit Agarwal <quic_rohiagar@quicinc.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
<catalin.marinas@arm.com>, <will@kernel.org>,
<quic_bjorande@quicinc.com>, <geert+renesas@glider.be>,
<konrad.dybcio@linaro.org>, <arnd@arndb.de>,
<neil.armstrong@linaro.org>, <dmitry.baryshkov@linaro.org>,
<nfraprado@collabora.com>, <m.szyprowski@samsung.com>,
<u-kumar1@ti.com>, <peng.fan@nxp.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<kernel@quicinc.com>
Subject: Re: [PATCH v2 1/3] arm64: defconfig: Enable GCC for SDX75
Date: Thu, 16 Nov 2023 17:15:27 +0530 [thread overview]
Message-ID: <5ff90cc0-cb1d-4a5d-bf0d-fdff68cb4366@quicinc.com> (raw)
In-Reply-To: <4b8b486a-3bce-4b1d-b844-7d2dc499db0f@linaro.org>
On 11/16/2023 4:46 PM, Krzysztof Kozlowski wrote:
> On 16/11/2023 10:35, Rohit Agarwal wrote:
>> Enable Global Clock controller framework support for
>> Qualcomm's SDX75 SoC which is required to boot to console
>> on sdx75-idp platform.
> No, really, this is just one patch, not three. You do not enable a
> platform with one-by-one config patches.
Ok, Sure. Will combine it into a single patch.
Thanks,
Rohit.
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2023-11-16 11:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 9:35 [PATCH v2 0/3] Enable configs required to boot SDX75 Rohit Agarwal
2023-11-16 9:35 ` [PATCH v2 1/3] arm64: defconfig: Enable GCC for SDX75 Rohit Agarwal
2023-11-16 11:16 ` Krzysztof Kozlowski
2023-11-16 11:45 ` Rohit Agarwal [this message]
2023-11-16 9:35 ` [PATCH v2 2/3] arm64: defconfig: Enable pinctrl " Rohit Agarwal
2023-11-16 9:35 ` [PATCH v2 3/3] arm64: defconfig: Enable Interconnect " Rohit Agarwal
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=5ff90cc0-cb1d-4a5d-bf0d-fdff68cb4366@quicinc.com \
--to=quic_rohiagar@quicinc.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=geert+renesas@glider.be \
--cc=kernel@quicinc.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=neil.armstrong@linaro.org \
--cc=nfraprado@collabora.com \
--cc=peng.fan@nxp.com \
--cc=quic_bjorande@quicinc.com \
--cc=u-kumar1@ti.com \
--cc=will@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