All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
Cc: stable@vger.kernel.org
Subject: Re: Backports that remove FPU lazy-mode deadcode for 4.9.y
Date: Fri, 13 Jul 2018 16:58:09 +0200	[thread overview]
Message-ID: <20180713145809.GA20331@kroah.com> (raw)
In-Reply-To: <1531354594-2236-1-git-send-email-daniel.sangorrin@toshiba.co.jp>

On Thu, Jul 12, 2018 at 09:16:33AM +0900, Daniel Sangorrin wrote:
> Hello Greg,
> 
> Please consider this backport for 4.9.y. It completes the removal
> of FPU lazy-mode code, documentation and comments.
> 
> [PATCH v3 4.9] x86/fpu: Remove use_eager_fpu()
> 
> After applying the patch, please do the following:
> 	- cherry-pick: 3913cc350757 ("x86/fpu: Remove struct fpu::counter")
> 	- revert: f09a7b0eead7 ("perf: sync up x86/.../cpufeatures.h")
> 		- Because the modification in this patch actually belongs to e63650840e8b ("x86/fpu: Finish excising 'eagerfpu'")
> 	- cherry-pick: e63650840e8b ("x86/fpu: Finish excising 'eagerfpu'")

That's a major pain.

Tell me again why we are doing this for the stable trees?  What does
this buy us?  It's nice cleanups sure, but are these going to be needed
for future backports?  Something else?

thanks,

greg k-h

  parent reply	other threads:[~2018-07-13 15:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-12  0:16 Backports that remove FPU lazy-mode deadcode for 4.9.y Daniel Sangorrin
2018-07-12  0:16 ` [PATCH v3 4.9] x86/fpu: Remove use_eager_fpu() Daniel Sangorrin
2018-07-12  0:16   ` Daniel Sangorrin
2018-07-13 14:58 ` Greg KH [this message]
2018-07-18  2:35   ` Backports that remove FPU lazy-mode deadcode for 4.9.y Daniel Sangorrin
2018-10-11 15:08     ` '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=20180713145809.GA20331@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=daniel.sangorrin@toshiba.co.jp \
    --cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.