From: Borislav Petkov <bp@alien8.de>
To: Andy Lutomirski <luto@kernel.org>
Cc: "Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Greg KH" <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"Rik van Riel" <riel@surriel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
"Ard Biesheuvel" <ard.biesheuvel@linaro.org>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"Ingo Molnar" <mingo@redhat.com>,
"Nicolai Stange" <nstange@suse.de>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>, "X86 ML" <x86@kernel.org>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH] x86/fpu: Remove the _GPL from the kernel_fpu_begin/end() export
Date: Thu, 2 May 2019 18:55:20 +0200 [thread overview]
Message-ID: <20190502165520.GC6565@zn.tnic> (raw)
In-Reply-To: <CALCETrWTCB9xLVdKCODghpeQpJ_3Rz3OwE8FB+5hjYXMYwYPLg@mail.gmail.com>
On Thu, May 02, 2019 at 09:29:01AM -0700, Andy Lutomirski wrote:
> I'm not saying that we should export things for ZFS's benefit. But,
> as far as I know, _GPL means "this interface is sufficiently specific
> to Linux details that we think that any user must be a derived work".
> I don't think that kernel_fpu_begin() is an example of that.
But it is sufficiently specific. It is present on x86 and s390 only -
other arches don't have it.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-05-02 16:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 14:42 [PATCH] x86/fpu: Remove the _GPL from the kernel_fpu_begin/end() export Andy Lutomirski
2019-05-02 15:40 ` Sebastian Andrzej Siewior
2019-05-02 16:29 ` Andy Lutomirski
2019-05-02 16:55 ` Borislav Petkov [this message]
2019-05-03 17:21 ` Paolo Bonzini
2019-05-03 18:07 ` Borislav Petkov
2019-05-03 18:54 ` Andy Lutomirski
2019-05-03 19:07 ` Borislav Petkov
2019-05-03 18:49 ` Jiri Kosina
2019-05-04 0:47 ` Ingo Molnar
2019-05-04 2:28 ` Sebastian Gottschall
2019-05-04 6:40 ` Greg KH
2019-05-05 16:05 ` Rik van Riel
2019-05-05 19:09 ` Jiri Kosina
2019-05-04 7:26 ` Jiri Kosina
2019-05-07 10:31 ` David Laight
2019-05-08 12:28 ` Sebastian Gottschall
2019-05-08 12:51 ` Greg KH
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=20190502165520.GC6565@zn.tnic \
--to=bp@alien8.de \
--cc=Jason@zx2c4.com \
--cc=ard.biesheuvel@linaro.org \
--cc=bigeasy@linutronix.de \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=nstange@suse.de \
--cc=pbonzini@redhat.com \
--cc=riel@surriel.com \
--cc=rkrcmar@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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