From: Yu-cheng Yu <yu-cheng.yu@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: dave.hansen@linux.intel.com, linux-kernel@vger.kernel.org,
ravi.v.shankar@intel.com, torvalds@linux-foundation.org,
haokexin@gmail.com, tglx@linutronix.de,
Joakim.Tjernlund@infinera.com, mingo@kernel.org,
peterz@infradead.org, hpa@zytor.com, fenghua.yu@intel.com,
luto@kernel.org, bp@suse.de, stable@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86/fpu/xstate: Fix xcomp_bv in XSAVES header
Date: Thu, 16 Feb 2017 09:51:49 -0800 [thread overview]
Message-ID: <20170216175148.GA29430@test-lenovo> (raw)
In-Reply-To: <20170216175112.GA13678@kroah.com>
On Thu, Feb 16, 2017 at 09:51:12AM -0800, Greg Kroah-Hartman wrote:
> On Tue, Feb 14, 2017 at 01:26:41PM -0800, Yu-cheng Yu wrote:
> > On Tue, Jan 24, 2017 at 12:46:17AM -0800, tip-bot for Yu-cheng Yu wrote:
> > > Commit-ID: dffba9a31c7769be3231c420d4b364c92ba3f1ac
> > > Gitweb: http://git.kernel.org/tip/dffba9a31c7769be3231c420d4b364c92ba3f1ac
> > > Author: Yu-cheng Yu <yu-cheng.yu@intel.com>
> > > AuthorDate: Mon, 23 Jan 2017 14:54:44 -0800
> > > Committer: Ingo Molnar <mingo@kernel.org>
> > > CommitDate: Tue, 24 Jan 2017 09:04:48 +0100
> > >
> > > x86/fpu/xstate: Fix xcomp_bv in XSAVES header
> I just tried to apply this, and it does not apply at all. Can you
> please provide a backported version that you have verified will work, so
> that I can apply it?
I will do that.
Thanks,
Yu-cheng
prev parent reply other threads:[~2017-02-16 17:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 22:54 [PATCH] x86/fpu/xstate: Fix xcomp_bv in XSAVES header Yu-cheng Yu
2017-01-24 8:09 ` Ingo Molnar
2017-02-02 20:18 ` Joakim Tjernlund
2017-01-24 8:46 ` [tip:x86/urgent] " tip-bot for Yu-cheng Yu
2017-02-14 21:26 ` Yu-cheng Yu
2017-02-14 22:53 ` Greg Kroah-Hartman
2017-02-16 17:51 ` Greg Kroah-Hartman
2017-02-16 17:51 ` Yu-cheng Yu [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=20170216175148.GA29430@test-lenovo \
--to=yu-cheng.yu@intel.com \
--cc=Joakim.Tjernlund@infinera.com \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=fenghua.yu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=haokexin@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.v.shankar@intel.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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.