From: Luis Chamberlain <mcgrof@kernel.org>
To: Werner Sembach <wse@tuxedocomputers.com>
Cc: u.kleine-koenig@baylibre.com, petr.pavlu@suse.com,
samitolvanen@google.com, da.gomez@samsung.com,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@leemhuis.info, vv@tuxedocomputers.com, cs@tuxedo.de,
"Uwe Kleine-König" <ukleinek@kernel.org>
Subject: Re: [PATCH v5 2/2] module: Block a module by TUXEDO from accessing GPL symbols
Date: Mon, 18 Nov 2024 12:53:43 -0800 [thread overview]
Message-ID: <ZzupV6H_Jy2Zhryp@bombadil.infradead.org> (raw)
In-Reply-To: <0f663358-e5e1-452b-8280-0be90ae7e7de@tuxedocomputers.com>
On Mon, Nov 18, 2024 at 11:10:28AM +0100, Werner Sembach wrote:
> Hi,
>
> Am 15.11.24 um 19:50 schrieb Werner Sembach:
> > From: Uwe Kleine-König <ukleinek@kernel.org>
> >
> > TUXEDO has not yet relicensed a module for GPLv2+ as a reply from former
> > contributers the committed code under GPLv3+ is awaited.
> >
> > Teach the module loader that this module is not GPLv2 compatible despite
> > the declaration to be GPLv2 compatible until the relicensing is complete.
>
> The relicensing is complete so this patch can be dropped entierly
Good to hear this has been resolved, the first patch is still a nice
cleanup so I'll take that in after the merge window, there's no need
to rush that in.
Lis
prev parent reply other threads:[~2024-11-18 20:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 18:50 [PATCH v5 2/2] module: Block a module by TUXEDO from accessing GPL symbols Werner Sembach
2024-11-15 18:50 ` [PATCH v5 1/2] module: Put known GPL offenders in an array Werner Sembach
2024-11-15 18:50 ` [PATCH v5 2/2] module: Block a module by TUXEDO from accessing GPL symbols Werner Sembach
2024-11-16 8:15 ` Daniel Gomez
2024-11-16 17:20 ` Uwe Kleine-König
2024-11-18 9:05 ` Daniel Gomez
2024-11-18 14:03 ` Greg Kroah-Hartman
2024-11-18 10:10 ` Werner Sembach
2024-11-18 20:53 ` Luis Chamberlain [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=ZzupV6H_Jy2Zhryp@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=cs@tuxedo.de \
--cc=da.gomez@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=ukleinek@kernel.org \
--cc=vv@tuxedocomputers.com \
--cc=wse@tuxedocomputers.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;
as well as URLs for NNTP newsgroup(s).