From: Tom Zanussi <zanussi@kernel.org>
To: Karim Yaghmour <karim.yaghmour@opersys.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: linux-spdx@vger.kernel.org
Subject: Re: relay: License cleanup
Date: Tue, 24 May 2022 15:28:42 -0500 [thread overview]
Message-ID: <c9a6c3685b9817126044cd733c57cbe9f228f4eb.camel@kernel.org> (raw)
In-Reply-To: <ea34a747-2393-142e-3352-74426975f6f5@opersys.com>
Hi Thomas and Karim,
On Sun, 2022-05-22 at 14:14 -0400, Karim Yaghmour wrote:
> Hi Thomas,
>
> On 5/22/22 10:54, Thomas Gleixner wrote:
> > Tom, Karim!
> >
> > As you might know we are working on cleaning up the licensing mess
> > in the
> > kernel and convert it to SPDX license identifiers as the only
> > source of
> > license information.
> >
> > Archaeology found unspecific GPL license references, which have
> > been
> > authored by you.
> >
> > 1) this file is released under the gpl
> >
> > kernel/relay.c
> >
> > Can you please either send cleanup patches for the affected files
> > or
> > indicate which GPLv2 variant you had in mind and I run it through
> > my
> > cleanup machinery.
>
> Thanks for the ping.
>
> I assume you mean the GPLv2 variants from here:
>
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/LICENSES/preferred/GPL-2.0?h=v5.18-rc7
>
> In that case, I'd say that the intent was to follow what Linus had
> been
> using: i.e. GPL-2.0 or GPL-2.0-only.
>
> That said, since it was Tom that got this code included and did most
> of
> the work on it, I think he'd have to confirm what his view was as
> well.
Yes, GPL-2.0-only was the intent, so please use that and run it through
your cleanup machinery, thanks.
Or I can send a cleanup patch if that's easier for you, just let me
know.
Thanks,
Tom
>
> Cheers,
>
prev parent reply other threads:[~2022-05-24 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 14:54 relay: License cleanup Thomas Gleixner
2022-05-22 18:14 ` Karim Yaghmour
2022-05-24 20:28 ` Tom Zanussi [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=c9a6c3685b9817126044cd733c57cbe9f228f4eb.camel@kernel.org \
--to=zanussi@kernel.org \
--cc=karim.yaghmour@opersys.com \
--cc=linux-spdx@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).