From: Borislav Petkov <bp@suse.de>
To: Andy Lutomirski <luto@kernel.org>
Cc: gregkh@linuxfoundation.org, dave.hansen@linux.intel.com,
riel@surriel.com, tglx@linutronix.de, stable@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] x86/fpu: Invalidate FPU state after a failed XRSTOR from a" failed to apply to 5.4-stable tree
Date: Mon, 21 Jun 2021 21:34:40 +0200 [thread overview]
Message-ID: <YNDp0GXOi/JQ4pse@zn.tnic> (raw)
In-Reply-To: <5c9dc791-f34e-e26e-9d34-7f5280d3990f@kernel.org>
On Mon, Jun 21, 2021 at 11:42:01AM -0700, Andy Lutomirski wrote:
> I agree. The fixes line is indeed wrong, and the (horribly misnamed)
> fpu_deactivate() call did the right thing.
Thanks!
@gregkh, then, you can ignore that one for 5.4.
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
prev parent reply other threads:[~2021-06-21 19:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 10:51 FAILED: patch "[PATCH] x86/fpu: Invalidate FPU state after a failed XRSTOR from a" failed to apply to 5.4-stable tree gregkh
2021-06-21 14:29 ` Borislav Petkov
2021-06-21 18:42 ` Andy Lutomirski
2021-06-21 19:34 ` Borislav Petkov [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=YNDp0GXOi/JQ4pse@zn.tnic \
--to=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=riel@surriel.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.