From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/gnu-efi: fix license information
Date: Sat, 3 Oct 2026 18:16:55 +0200 [thread overview]
Message-ID: <asEqc-3L7USj_G5X@windsurf> (raw)
In-Reply-To: <20260923182403.2143949-1-fiona.klute@gmx.de>
On Wed, Sep 23, 2026 at 08:24:03PM +0200, Fiona Klute via buildroot wrote:
> From: "Fiona Klute (othermo GmbH)" <fiona.klute@gmx.de>
>
> Split the confusing "and/or" for gnulib, so dual-licensed and GPL-only
> parts are clearly noted, and add the missing LGPL license. Lines in
> GNU_EFI_LICENSE are ordered the same way as the information is given
> in the LICENSE file.
>
> The license situation of inc/subst/elf.h is curious: The file itself
> is licensed under LGPL-2.1-or-later, and used in gnu-efi under
> LGPL-3.0-or-later (accompanied by the appropriate license files),
> which in turn allows using it for object code under different terms
> with certain conditions (see section 3 of LGPL 3.0, as noted in the
> gnu-efi LICENSE file).
>
> Signed-off-by: Fiona Klute (othermo GmbH) <fiona.klute@gmx.de>
Applied to master, thanks!
Best regards,
Thomas Petazzoni
--
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
next prev parent reply other threads:[~2026-10-03 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 18:24 [Buildroot] [PATCH 1/1] package/gnu-efi: fix license information Fiona Klute via buildroot
2026-10-03 16:16 ` Thomas Petazzoni via buildroot [this message]
2026-10-10 9:23 ` Thomas Perale via buildroot
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=asEqc-3L7USj_G5X@windsurf \
--to=buildroot@buildroot.org \
--cc=fiona.klute@gmx.de \
--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