From: Werner Sembach <wse@tuxedocomputers.com>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Luis Chamberlain <mcgrof@kernel.org>,
tux@tuxedocomputers.com, Petr Pavlu <petr.pavlu@suse.com>,
Sami Tolvanen <samitolvanen@google.com>,
Daniel Gomez <da.gomez@samsung.com>,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
Thorsten Leemhuis <linux@leemhuis.info>,
Vinzenz Vietzke <vv@tuxedocomputers.com>,
Christoffer Sandberg <cs@tuxedo.de>
Subject: Re: [PATCH 0/2] module: Block modules by Tuxedo from accessing GPL symbols
Date: Fri, 15 Nov 2024 12:01:43 +0100 [thread overview]
Message-ID: <9e498b77-acfc-4aca-9734-16d5829518d4@tuxedocomputers.com> (raw)
In-Reply-To: <y3lspnzleavkgvujrf66rly65yw3sskjomcvbginijgexaybys@bg53hyadhcbw>
Am 15.11.24 um 11:51 schrieb Uwe Kleine-König:
> Hello Werner,
>
> On Fri, Nov 15, 2024 at 10:40:56AM +0100, Werner Sembach wrote:
>> Then why does the proprietary NVIDIA driver exist?
> Please don't use NVIDIA's behaviour as a blueprint for your actions.
> INAL, but I would not recommend to deduce from "NVIDIA does it and
> wasn't tried to stop" (for any value of "it") that "it" is legal, honest
> and in line with the open source spirit.
Ofc I don't want to use NVIDIA's behavior as a blueprint, it was just to show
where my misconception stems from.
>
> Best regards
> Uwe
next prev parent reply other threads:[~2024-11-15 11:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241114103151eucas1p133de0b231bf06bf8cd42621347a0ed17@eucas1p1.samsung.com>
2024-11-14 10:31 ` Uwe Kleine-König
2024-11-14 10:31 ` [PATCH 1/2] module: Put known GPL offenders in an array Uwe Kleine-König
2024-11-14 16:08 ` Christoph Hellwig
2024-11-15 4:40 ` Greg KH
2024-11-14 10:31 ` [PATCH 2/2] module: Block modules by Tuxedo from accessing GPL symbols Uwe Kleine-König
2024-11-14 11:56 ` Daniel Gomez
2024-11-15 4:40 ` Greg KH
2024-11-14 16:09 ` Christoph Hellwig
2024-11-14 19:21 ` Aaron Rainbolt
2024-11-14 23:06 ` Al Viro
2024-11-15 4:40 ` Greg KH
2024-11-18 10:11 ` Werner Sembach
2024-11-14 10:49 ` [PATCH 0/2] " Werner Sembach
2024-11-14 11:14 ` Uwe Kleine-König
2024-11-14 11:44 ` Werner Sembach
2024-11-16 17:49 ` Uwe Kleine-König
2024-11-16 18:41 ` Werner Sembach
2024-11-15 4:43 ` Greg KH
2024-11-15 6:09 ` Werner Sembach
2024-11-15 6:30 ` Greg KH
2024-11-15 7:29 ` Uwe Kleine-König
2024-11-15 9:00 ` Werner Sembach
2024-11-15 9:18 ` Greg KH
2024-11-15 9:40 ` Werner Sembach
2024-11-15 10:22 ` Greg KH
2024-11-15 10:59 ` Werner Sembach
2024-11-15 12:01 ` Greg KH
2024-11-15 10:51 ` Uwe Kleine-König
2024-11-15 11:01 ` Werner Sembach [this message]
2024-11-14 11:50 ` Daniel Gomez
2024-11-20 14:11 ` Hans de Goede
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=9e498b77-acfc-4aca-9734-16d5829518d4@tuxedocomputers.com \
--to=wse@tuxedocomputers.com \
--cc=cs@tuxedo.de \
--cc=da.gomez@samsung.com \
--cc=gregkh@linuxfoundation.org \
--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=tux@tuxedocomputers.com \
--cc=u.kleine-koenig@baylibre.com \
--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®