From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 4/4] package/gnu-efi: change upstream, bump to 4.0.0
Date: Sun, 19 Jan 2025 13:36:45 +0100 [thread overview]
Message-ID: <20250119133645.5b481c1c@windsurf> (raw)
In-Reply-To: <8cb7eeb2adac1069fd2d6fcb8565df66@free.fr>
Hello Julien,
On Sun, 19 Jan 2025 13:32:02 +0100
Julien Olivain <ju.o@free.fr> wrote:
> Thanks for the patches! I applied patches 1 to 3 of this series.
Thanks!
> For this patch, "make gnu-efi-legal-info" is failing. See below.
[...]
> Can you send a v2 with those license info updated, please?
Dammit, I had forgotten about the basics. Thanks for spotting this, I
will review the legal-info details, and send a v2.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-01-19 12:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-19 8:45 [Buildroot] [PATCH 0/4] syslinux and gnu-efi fixes and update Thomas Petazzoni via buildroot
2025-01-19 8:45 ` [Buildroot] [PATCH 1/4] support/testing/tests/boot/test_syslinux: use newer toolchains Thomas Petazzoni via buildroot
2025-01-19 12:24 ` Julien Olivain
2025-01-19 8:45 ` [Buildroot] [PATCH 2/4] boot/syslinux: add multiple patches fixing build issues with GCC >= 14 Thomas Petazzoni via buildroot
2025-01-19 12:24 ` Julien Olivain
2025-01-31 16:43 ` Peter Korsgaard
2025-01-19 8:45 ` [Buildroot] [PATCH 3/4] package/gnu-efi: fix build due to short-wchar Thomas Petazzoni via buildroot
2025-01-19 12:25 ` Julien Olivain
2025-01-31 16:44 ` Peter Korsgaard
2025-01-19 8:45 ` [Buildroot] [PATCH 4/4] package/gnu-efi: change upstream, bump to 4.0.0 Thomas Petazzoni
2025-01-19 12:32 ` Julien Olivain
2025-01-19 12:36 ` Thomas Petazzoni 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=20250119133645.5b481c1c@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.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