From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Suresh Siddha <suresh.b.siddha@intel.com>,
linux-kernel@vger.kernel.org, mingo@elte.hu,
stable@vger.kernel.org
Subject: Re: Don't apply 9f022e54b8ea82d1ecdf3bd78d9ab9f44d6b0655 to stable please.
Date: Tue, 3 Apr 2012 09:28:50 -0400 [thread overview]
Message-ID: <20120403132850.GE12464@phenom.dumpdata.com> (raw)
In-Reply-To: <20120402234904.GA18316@kroah.com>
> > Author: Suresh Siddha <suresh.b.siddha@intel.com>
> > Date: Mon Mar 12 11:36:33 2012 -0700
> >
> > x86/ioapic: Add register level checks to detect bogus io-apic entries
> >
> > With out this commit, if the bios lists bogus io-apic's, then we will
> > see some error messages ("Unable to reset IRR for apic")during linux
> > boot which are benign. But as this patch breaks Xen, I am ok if these
> > don't get applied to 'stable'. Also I think it is Ingo who added the
> > 'stable' tag. Ingo, are you ok with this?
>
> What stable trees did this already go into in the releases today?
I see it in v3.2.x as:
273fb19 x86/ioapic: Add register level checks to detect bogus io-apic entries
And in 3.0.x:
c2ec63e x86/ioapic: Add register level checks to detect bogus io-apic entries
But I don't see it in 3.1.x tree?
>
> You need to tell me what I need to revert here, SPECIFICALLY, and in
> what tree, if needed, otherwise I have no idea what is going on, sorry,
> I can't read minds.
next prev parent reply other threads:[~2012-04-03 13:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 22:47 Don't apply 9f022e54b8ea82d1ecdf3bd78d9ab9f44d6b0655 to stable please Konrad Rzeszutek Wilk
2012-04-02 23:02 ` Suresh Siddha
2012-04-02 23:27 ` Greg KH
2012-04-02 23:43 ` Suresh Siddha
2012-04-02 23:49 ` Greg KH
2012-04-03 13:04 ` Konrad Rzeszutek Wilk
2012-04-03 13:28 ` Konrad Rzeszutek Wilk [this message]
2012-04-03 14:26 ` Teck Choon Giam
2012-04-03 14:31 ` Konrad Rzeszutek Wilk
2012-04-03 14:56 ` Teck Choon Giam
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=20120403132850.GE12464@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stable@vger.kernel.org \
--cc=suresh.b.siddha@intel.com \
/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