mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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
Subject: Re: [PATCH v3 0/2] module: Block some modules by TUXEDO from accessing
Date: Fri, 15 Nov 2024 14:03:27 +0100	[thread overview]
Message-ID: <3023bbda-0902-4e5c-aeb1-074623cd8ff0@tuxedocomputers.com> (raw)
In-Reply-To: <20241115130139.1244786-1-wse@tuxedocomputers.com>

Am 15.11.24 um 13:58 schrieb Werner Sembach:
> Following the meeting I wrote about yesterday, I now changed the license
> of what we could change spontaniously to prove good faith.
>
> I still hope that the rest can be sorted out before anything gets merged.
> We are working on it. A clear time window would still be helpfull.
>
> At Uwe. I don't know how it works if you modifiy someone elses code. I
> removed the Signed-off-by: line and I guess you have to add it again?
>
> v2: Removed modules that could and have been spontaniously relicensed
> v3: Fix typo and remove untrue assumption while giving more context
>
Wrong version in the cover letter, but should be no problem should it?

I need to grab lunch ...



  parent reply	other threads:[~2024-11-15 13:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-15 12:58 [PATCH v2 " Werner Sembach
2024-11-15 12:58 ` [PATCH v3 1/2] module: Put known GPL offenders in an array Werner Sembach
2024-11-15 12:58 ` [PATCH v3 2/2] module: Block some modules by TUXEDO from accessing GPL symbols Werner Sembach
2024-11-15 13:03 ` Werner Sembach [this message]
2024-11-15 16:40   ` [PATCH v3 0/2] module: Block some modules by TUXEDO from accessing Uwe Kleine-König
2024-11-15 17:27     ` Werner Sembach

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=3023bbda-0902-4e5c-aeb1-074623cd8ff0@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=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®