From: Werner Sembach <wse@tuxedocomputers.com>
To: u.kleine-koenig@baylibre.com, mcgrof@kernel.org,
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
Cc: "Uwe Kleine-König" <ukleinek@kernel.org>,
"Werner Sembach" <wse@tuxedocomputers.com>
Subject: [PATCH v2 2/2] module: Block some modules by TUXEDO from accessing GPL symbols
Date: Fri, 15 Nov 2024 13:49:40 +0100 [thread overview]
Message-ID: <20241115125121.1242871-3-wse@tuxedocomputers.com> (raw)
In-Reply-To: <20241115125121.1242871-1-wse@tuxedocomputers.com>
From: Uwe Kleine-König <ukleinek@kernel.org>
TUXEDO has not yet relicend all modules for GPLv2+ as former contributer
need to be contacted that comited code under GPLv3+.
So teach the module loader that these modules are proprietary despite
their declaration to be GPLv2 compatible until the relicensing is complete.
Signed-off-by: Werner Sembach <wse@tuxedocomputers.com>
---
kernel/module/main.c | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/kernel/module/main.c b/kernel/module/main.c
index 905d7b60dd709..3f391183aaf97 100644
--- a/kernel/module/main.c
+++ b/kernel/module/main.c
@@ -2029,6 +2029,29 @@ static const char *module_license_offenders[] = {
/* lve claims to be GPL but upstream won't provide source */
"lve",
+
+ /*
+ * Tuxedo distributes their kernel modules under GPLv3, but intentially
+ * lies in their MODULE_LICENSE() calls.
+ * See https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers/-/commit/a8c09b6c2ce6393fe39d8652d133af9f06cfb427
+ */
+ "tuxedo_io",
+ "tuxedo_nb04_keyboard",
+ "tuxedo_nb04_wmi_ab",
+ "tuxedo_nb04_wmi_bs",
+ "tuxedo_nb04_sensors",
+ "tuxedo_nb04_power_profiles",
+ "tuxedo_nb04_kbd_backlight",
+ "tuxedo_nb05_keyboard",
+ "tuxedo_nb05_kbd_backlight",
+ "tuxedo_nb05_power_profiles",
+ "tuxedo_nb05_ec",
+ "tuxedo_nb05_sensors",
+ "tuxedo_nb05_fan_control",
+ "clevo_wmi",
+ "tuxedo_keyboard",
+ "clevo_acpi",
+ "uniwill_wmi",
};
/*
--
2.43.0
prev parent reply other threads:[~2024-11-15 12:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 12:49 [PATCH v2 0/2] module: Block some modules by TUXEDO from accessing Werner Sembach
2024-11-15 12:49 ` [PATCH v2 1/2] module: Put known GPL offenders in an array Werner Sembach
2024-11-15 12:49 ` Werner Sembach [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=20241115125121.1242871-3-wse@tuxedocomputers.com \
--to=wse@tuxedocomputers.com \
--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=mcgrof@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=ukleinek@kernel.org \
--cc=vv@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
all inboxes | Powered by JetHome®