From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Daniel Gomez <da.gomez@samsung.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Daniel Gomez" <d+samsung@kruces.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Werner Sembach" <wse@tuxedocomputers.com>,
mcgrof@kernel.org, petr.pavlu@suse.com, samitolvanen@google.com,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@leemhuis.info, vv@tuxedocomputers.com, cs@tuxedo.de,
linux-spdx@vger.kernel.org
Subject: Re: [PATCH v5 2/2] module: Block a module by TUXEDO from accessing GPL symbols
Date: Mon, 18 Nov 2024 15:03:39 +0100 [thread overview]
Message-ID: <2024111821-gathering-storage-04c3@gregkh> (raw)
In-Reply-To: <D5P6NQ9ZWP13.K9G49CLMO6LV@samsung.com>
On Mon, Nov 18, 2024 at 10:05:27AM +0100, Daniel Gomez wrote:
> Thomas, Greg, are we using any specific SPDX version for kernel license
> identifiers? Why the new identifiers where amended as valid and not
> replacing [2] the old ones? Was it to avoid replacing all files with the
> old id?
Yes it was. Let's worry about getting all files in the kernel properly
tagged before even considering moving to newer versions of the SPDX
specification. When we started this, we used the most up to date tags,
but then they changed, and we didn't want to change all of the kernel
while half-way in the middle of the conversion.
Just leave it as-is please.
thanks,
greg k-h
prev parent reply other threads:[~2024-11-18 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241115185253.1299264-1-wse@tuxedocomputers.com>
[not found] ` <20241115185253.1299264-3-wse@tuxedocomputers.com>
[not found] ` <D5NGCPSP7EO8.28YI337NY203X@kruces.com>
[not found] ` <CGME20241116172026eucas1p2ae18643501640a7c6a3a796c30b60fed@eucas1p2.samsung.com>
[not found] ` <wnfqe7q2aby76zokkh77jhlwc2dbr243kycmejc4wj5wflywgi@6sox742ip22g>
2024-11-18 9:05 ` [PATCH v5 2/2] module: Block a module by TUXEDO from accessing GPL symbols Daniel Gomez
2024-11-18 14:03 ` Greg Kroah-Hartman [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=2024111821-gathering-storage-04c3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cs@tuxedo.de \
--cc=d+samsung@kruces.com \
--cc=da.gomez@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=mcgrof@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@baylibre.com \
--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