[lkml]   [2012]   [Apr]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Don't apply 9f022e54b8ea82d1ecdf3bd78d9ab9f44d6b0655 to stable please.
On Mon, 2012-04-02 at 16:27 -0700, Greg KH wrote:
> On Mon, Apr 02, 2012 at 06:47:02PM -0400, Konrad Rzeszutek Wilk wrote:
> > Hey Greg,
> >
> > The git commit 9f022e54b8ea82d1ecdf3bd78d9ab9f44d6b0655 has CC
> > but it breaks Xen - we are working to fix it in 3.4, but the fix for it
> > does some architectual changes (136d249ef7dbf0fefa292082cc40be1ea864cbd6) that
> > I don't know if you are comfortable putting in stable tree.
> >
> I have no idea what that git commit id referrs to, as it's not in
> Linus's tree at the moment.
> Care to give me a subject? diffstat? Some kind of hint?

Greg, Konrad is referring to:

commit 73d63d038ee9f769f5e5b46792d227fe20e442c5
Author: Suresh Siddha <>
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?

For the mainline, we have queued more patches to fix the Xen breakage.


> And note, you forgot to send this to the list,
> where the other stable kernel maintainers live, please do so next time.
> thanks,
> greg k-h

 \ /
  Last update: 2012-04-03 01:43    [W:0.136 / U:2.640 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site