From: Mason Loring Bliss <mason@blisses.org>
To: Devel <zfs-devel@list.zfsonlinux.org>
Cc: Aleksa Sarai <cyphar@cyphar.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Rik van Riel <riel@surriel.com>, Nicolai Stange <nstange@suse.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [zfs-devel] Re: [PATCH] x86/fpu: allow kernel_fpu_{begin,end} to be used by non-GPL modules
Date: Thu, 23 May 2019 12:52:56 -0400 [thread overview]
Message-ID: <20190523165256.GD8766@blisses.org> (raw)
In-Reply-To: <20190522100959.GA15390@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 630 bytes --]
On Wed, May 22, 2019 at 12:09:59PM +0200, Greg KH wrote:
> No, please, we have gone over this before, we do not care at all about
> external kernel modules, ESPECIALLY ones that are not GPL compatible.
The best option here is for you to start caring. Makes the world a better
place.
Free software people doing what they can to attack other free software based
on relatively trivial idealogical differences isn't a good look, and it's bad
for the users.
--
Mason Loring Bliss (( If I have not seen as far as others, it is because
mason@blisses.org )) giants were standing on my shoulders. - Hal Abelson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-05-23 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 4:42 [PATCH] x86/fpu: allow kernel_fpu_{begin,end} to be used by non-GPL modules Aleksa Sarai
2019-05-22 10:09 ` Greg KH
2019-05-23 16:52 ` Mason Loring Bliss [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=20190523165256.GD8766@blisses.org \
--to=mason@blisses.org \
--cc=Jason@zx2c4.com \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=cyphar@cyphar.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nstange@suse.de \
--cc=riel@surriel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=zfs-devel@list.zfsonlinux.org \
/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 NNTP newsgroup(s).