From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@amd.com>
Cc: buildroot@buildroot.org, ibai.erkiaga-elorza@amd.com,
luca.ceresoli@bootlin.com, yann.morin@orange.com,
brandon.maier@collins.com, thomas.petazzoni@bootlin.com,
romain.naour@smile.fr, michal.simek@amd.com,
romain.naour@gmail.com
Subject: Re: [Buildroot] [PATCH v2 1/1] boot/xilinx-prebuilt: simplify family logic
Date: Tue, 30 Sep 2025 21:30:24 +0200 [thread overview]
Message-ID: <53398ca895cb5c23aaa8530507340fb4@free.fr> (raw)
In-Reply-To: <20250930125823.971241-1-neal.frager@amd.com>
On 30/09/2025 14:58, Neal Frager via buildroot wrote:
> Currently, the xilinx-prebuilt package uses an if-then-else statement
> for
> deciding which files need to be installed from the xilinx-prebuilt
> repo. This
> works fine for now because there are really only two options, either
> versal or
> zynqmp/kria.
>
> Starting with the xilinx_v2025.2 release, the versal2 family along with
> the
> vek385 board will be added to Buildroot and thus the xilinx-prebuilt
> package
> as well. In the future, additional families will also probably be added
> to
> this package.
>
> To avoid creating a long if-then-else-then-else statement which will
> only grow
> in complexity over time, simplify the logic of the xilinx-prebuilt
> package by
> giving each xilinx family its own if statement. In the long term, this
> will
> make the xilinx-prebuilt package easier to understand and maintain.
>
> For this reason, this patch moves the zynqmp/kria families from the
> "else"
> statement to having an if statement separate from the versal family.
>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-09-30 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 12:58 [Buildroot] [PATCH v2 1/1] boot/xilinx-prebuilt: simplify family logic Neal Frager via buildroot
2025-09-30 16:33 ` Luca Ceresoli via buildroot
2025-09-30 19:30 ` Julien Olivain via buildroot [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=53398ca895cb5c23aaa8530507340fb4@free.fr \
--to=buildroot@buildroot.org \
--cc=brandon.maier@collins.com \
--cc=ibai.erkiaga-elorza@amd.com \
--cc=ju.o@free.fr \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=romain.naour@gmail.com \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin@orange.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