From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Neal Frager via buildroot <buildroot@buildroot.org>
Cc: Neal Frager <neal.frager@amd.com>,
ibai.erkiaga-elorza@amd.com, luca.ceresoli@bootlin.com,
brandon.maier@collins.com, ju.o@free.fr, romain.naour@smile.fr,
michal.simek@amd.com
Subject: Re: [Buildroot] [PATCH v1 1/1] package/bootgen: bump to xilinx_v2025.1
Date: Fri, 30 May 2025 21:36:30 +0200 [thread overview]
Message-ID: <20250530213630.2460a742@windsurf> (raw)
In-Reply-To: <20250530164017.473549-1-neal.frager@amd.com>
On Fri, 30 May 2025 17:40:17 +0100
Neal Frager via buildroot <buildroot@buildroot.org> wrote:
> Bump bootgen to xilinx_v2025.1 release.
>
> With version 2025.1, bootgen executable is now in the build/bin dir, so
> the install step is changed accordingly.
>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
> ---
> package/bootgen/bootgen.hash | 4 ++--
> package/bootgen/bootgen.mk | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
Applied to next, thanks. You had forgotten to explain why the hash of
the LICENSE file had changed, so I added a not in the commit log about
this.
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-05-30 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 16:40 [Buildroot] [PATCH v1 1/1] package/bootgen: bump to xilinx_v2025.1 Neal Frager via buildroot
2025-05-30 19:36 ` Thomas Petazzoni via buildroot [this message]
2025-06-02 11:47 ` Peter Korsgaard
2025-06-02 11:57 ` Frager, Neal via buildroot
2025-06-02 12:12 ` Peter Korsgaard
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=20250530213630.2460a742@windsurf \
--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@smile.fr \
--cc=thomas.petazzoni@bootlin.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