From: Greg KH <gregkh@linuxfoundation.org>
To: Borislav Petkov <bp@alien8.de>
Cc: tglx@linutronix.de, akataria@vmware.com, bigeasy@linutronix.de,
boris.ostrovsky@oracle.com, ciwillia@brocade.com,
m.v.b@runbox.com, peterz@infradead.org, stable@vger.kernel.org,
stable-commits@vger.kernel.org
Subject: Re: Patch "x86/cpu: Deal with broken firmware (VMWare/XEN)" has been added to the 4.8-stable tree
Date: Tue, 22 Nov 2016 18:08:07 +0100 [thread overview]
Message-ID: <20161122170807.GB20022@kroah.com> (raw)
In-Reply-To: <20161122150458.ymn4pteiiip5zk3s@pd.tnic>
On Tue, Nov 22, 2016 at 04:04:58PM +0100, Borislav Petkov wrote:
> On Mon, Nov 21, 2016 at 11:56:22AM +0100, gregkh@linuxfoundation.org wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > x86/cpu: Deal with broken firmware (VMWare/XEN)
> >
> > to the 4.8-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > x86-cpu-deal-with-broken-firmware-vmware-xen.patch
> > and it can be found in the queue-4.8 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
> Yes, please remove it from the stable queue for now. We'll have a fix ontop
> first and we'll submit both then as the check
>
> if (apicid != c->initial_apicid) {
>
> fires on pretty much everything-AMD now.
Now removed, thanks for letting me know.
greg k-h
prev parent reply other threads:[~2016-11-22 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 10:56 Patch "x86/cpu: Deal with broken firmware (VMWare/XEN)" has been added to the 4.8-stable tree gregkh
2016-11-22 15:04 ` Borislav Petkov
2016-11-22 17:08 ` 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=20161122170807.GB20022@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akataria@vmware.com \
--cc=bigeasy@linutronix.de \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=ciwillia@brocade.com \
--cc=m.v.b@runbox.com \
--cc=peterz@infradead.org \
--cc=stable-commits@vger.kernel.org \
--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 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).