From: Dinh Nguyen <dinguyen@kernel.org>
To: tze.yee.ng@altera.com, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: adrian.ho.yin.ng@altera.com,
muhammad.nazim.amirul.nazle.asmade@altera.com
Subject: Re: [PATCH] arm64: dts: socfpga: use consistent QSPI boot partition label
Date: Thu, 14 May 2026 06:58:36 -0500 [thread overview]
Message-ID: <4b74eb09-4265-47ac-93fb-f6ad7f231b04@kernel.org> (raw)
In-Reply-To: <eff34df0c67d39a26d20ec91eda8dd9e15f9f5cc.1778658884.git.tze.yee.ng@altera.com>
On 5/13/26 03:05, tze.yee.ng@altera.com wrote:
> From: Tze Yee Ng <tze.yee.ng@altera.com>
>
> Several SoCFPGA board DTS files labeled the first QSPI MTD partition
> (qspi_boot / partition@0 under fixed-partitions) as "u-boot" while
> others already used "Boot and fpga data". Align the QSPI boot
> partition label only so naming matches the combined boot + FPGA
> image layout and stays consistent across Agilex, N5X, and Stratix 10
> SoCDK variants.
>
> No QSPI partition layout or reg properties are changed.
>
> Signed-off-by: Tze Yee Ng <tze.yee.ng@altera.com>
> ---
> arch/arm64/boot/dts/intel/socfpga_agilex3_socdk.dts | 2 +-
> arch/arm64/boot/dts/intel/socfpga_agilex5_socdk.dts | 2 +-
> arch/arm64/boot/dts/intel/socfpga_agilex5_socdk_013b.dts | 2 +-
> arch/arm64/boot/dts/intel/socfpga_agilex5_socdk_modular.dts | 2 +-
> 4 files changed, 4 insertions(+), 4 deletions(-)
>
Applied!
Thanks,
Dinh
prev parent reply other threads:[~2026-05-14 11:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 8:05 [PATCH] arm64: dts: socfpga: use consistent QSPI boot partition label tze.yee.ng
2026-05-14 2:44 ` sashiko-bot
2026-05-14 6:22 ` NG, TZE YEE
2026-05-14 11:58 ` Dinh Nguyen [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=4b74eb09-4265-47ac-93fb-f6ad7f231b04@kernel.org \
--to=dinguyen@kernel.org \
--cc=adrian.ho.yin.ng@altera.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=muhammad.nazim.amirul.nazle.asmade@altera.com \
--cc=robh@kernel.org \
--cc=tze.yee.ng@altera.com \
/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