From: Thomas Gleixner <tglx@linutronix.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: avagin@google.com, bogomolov@google.com,
dave.hansen@linux.intel.com, stable@vger.kernel.org
Subject: Re: [PATCH linux-5.15.y] x86/fpu: Stop relying on userspace for info to fault in xsave
Date: Sun, 25 Feb 2024 19:54:12 +0100 [thread overview]
Message-ID: <8734tgcr3f.ffs@tglx> (raw)
In-Reply-To: <2024022312-bulginess-contend-ac94@gregkh>
On Fri, Feb 23 2024 at 17:04, Greg KH wrote:
> Nit, you forgot to give me a hint what the git id was :(
Ooops. Sorry.
> I figured it out, now queued up, thanks.
Thank you!
Thomas
prev parent reply other threads:[~2024-02-25 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 18:24 FAILED: patch "[PATCH] x86/fpu: Stop relying on userspace for info to fault in xsave" failed to apply to 5.15-stable tree gregkh
2024-02-21 20:29 ` [PATCH linux-5.15.y] x86/fpu: Stop relying on userspace for info to fault in xsave Thomas Gleixner
2024-02-23 16:04 ` Greg KH
2024-02-25 18:54 ` Thomas Gleixner [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=8734tgcr3f.ffs@tglx \
--to=tglx@linutronix.de \
--cc=avagin@google.com \
--cc=bogomolov@google.com \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--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 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).