public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Andy Lutomirski <luto@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	20181129150210.2k4mawt37ow6c2vq@linutronix.de,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Borislav Petkov <bp@suse.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
	Nicolai Stange <nstange@suse.de>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Rik van Riel <riel@surriel.com>,
	Radim Krcmar <rkrcmar@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>, X86 ML <x86@kernel.org>,
	stable-commits@vger.kernel.org
Subject: Re: Patch "x86/fpu: Don't export __kernel_fpu_{begin,end}()" has been added to the 4.19-stable tree
Date: Thu, 2 May 2019 16:54:10 +0200	[thread overview]
Message-ID: <20190502145410.GA13656@kroah.com> (raw)
In-Reply-To: <CALCETrXx_24vOLosXvOMZ81LKcAnud1A7axZ057wK0KFeBCT3A@mail.gmail.com>

On Thu, May 02, 2019 at 07:42:21AM -0700, Andy Lutomirski wrote:
> On Thu, May 2, 2019 at 1:02 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Wed, May 01, 2019 at 10:47:07AM -0700, Andy Lutomirski wrote:
> > > On Mon, Apr 29, 2019 at 6:36 AM <gregkh@linuxfoundation.org> wrote:
> > > >
> > > >
> > > > This is a note to let you know that I've just added the patch titled
> > > >
> > > >     x86/fpu: Don't export __kernel_fpu_{begin,end}()
> > > >
> > > > to the 4.19-stable tree which can be found at:
> > > >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > >
> > > Why?  ISTM the only possible effect is to break out-of-tree modules.
> > > I have no objection to breaking such modules if we need to, but, in
> > > this case, I don't see the benefit.
> >
> > The "benefit" is that people keep complaining that newer kernels do not
> > have this api for some reason and that it is a "regression", which
> > completely does not understand how the kernel handles internal apis.
> 
> I suppose that's a reasonable point.  But maybe we should actually
> give these modules a credible alternative first?  I just send a patch.

That's your call, it's your code :)

thanks,

greg k-h

      reply	other threads:[~2019-05-02 14:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1556544977149154@kroah.com>
     [not found] ` <CALCETrVjhVXYA4B6zFzbH14wBXZcNMAeM8YxdRh3RLHxVVde_g@mail.gmail.com>
     [not found]   ` <20190502080204.GA2832@kroah.com>
2019-05-02 14:42     ` Patch "x86/fpu: Don't export __kernel_fpu_{begin,end}()" has been added to the 4.19-stable tree Andy Lutomirski
2019-05-02 14:54       ` Greg KH [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=20190502145410.GA13656@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=20181129150210.2k4mawt37ow6c2vq@linutronix.de \
    --cc=Jason@zx2c4.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=bigeasy@linutronix.de \
    --cc=bp@suse.de \
    --cc=dave.hansen@linux.intel.com \
    --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-commits@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