From: Krzysztof Kozlowski <krzk@kernel.org>
To: Md Sadre Alam <quic_mdalam@quicinc.com>,
andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 6/6] arm64: dts: qcom: ipq5332-rdp442: Remove eMMC support
Date: Mon, 23 Feb 2026 16:00:00 +0100 [thread overview]
Message-ID: <106fe923-a840-40ba-9ec6-bd22f9897063@kernel.org> (raw)
In-Reply-To: <20260223100552.1050303-7-quic_mdalam@quicinc.com>
On 23/02/2026 11:05, Md Sadre Alam wrote:
> Remove eMMC support from the IPQ5332 RDP442 board configuration to
> align with the board's default NOR+NAND boot mode design.
>
> The IPQ5332 RDP442 board is designed with NOR+NAND as the default boot
> mode configuration. The eMMC and SPI NAND interface share
> same GPIO
This is not a separate patch and it makes no sense to do it separately.
You do it because you added NAND, so this is part of the NAND patch.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-23 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 10:05 [PATCH v5 0/6] Add QPIC SPI NAND support for IPQ5424 and IPQ5332 platforms Md Sadre Alam
2026-02-23 10:05 ` [PATCH v5 1/6] arm64: dts: qcom: ipq5424: Add QPIC SPI NAND controller support Md Sadre Alam
2026-02-23 10:05 ` [PATCH v5 2/6] arm64: dts: qcom: ipq5332: " Md Sadre Alam
2026-02-23 10:05 ` [PATCH v5 3/6] arm64: dts: qcom: ipq5424-rdp466: Enable QPIC SPI NAND support Md Sadre Alam
2026-02-23 10:05 ` [PATCH v5 4/6] arm64: dts: qcom: pq5332-rdp-common: " Md Sadre Alam
2026-02-23 10:05 ` [PATCH v5 5/6] arm64: dts: qcom: ipq5424-rdp466: Remove eMMC support Md Sadre Alam
2026-02-23 14:59 ` Krzysztof Kozlowski
2026-02-27 6:11 ` Md Sadre Alam
2026-02-23 10:05 ` [PATCH v5 6/6] arm64: dts: qcom: ipq5332-rdp442: " Md Sadre Alam
2026-02-23 15:00 ` Krzysztof Kozlowski [this message]
2026-02-27 6:14 ` Md Sadre Alam
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=106fe923-a840-40ba-9ec6-bd22f9897063@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=quic_mdalam@quicinc.com \
--cc=robh@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