mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	linux-kernel@vger.kernel.org, mingo@elte.hu,
	stable@vger.kernel.org
Subject: Re: Don't apply 9f022e54b8ea82d1ecdf3bd78d9ab9f44d6b0655 to stable please.
Date: Mon, 02 Apr 2012 16:43:05 -0700	[thread overview]
Message-ID: <1333410186.1270.92.camel@sbsiddha-desk.sc.intel.com> (raw)
In-Reply-To: <20120402232750.GB17821@kroah.com>

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 stable@kernel.org
> > 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 <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?

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

thanks,
suresh

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



  reply	other threads:[~2012-04-02 23:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02 22:47 Konrad Rzeszutek Wilk
2012-04-02 23:02 ` Suresh Siddha
2012-04-02 23:27 ` Greg KH
2012-04-02 23:43   ` Suresh Siddha [this message]
2012-04-02 23:49     ` Greg KH
2012-04-03 13:04       ` Konrad Rzeszutek Wilk
2012-04-03 13:28       ` Konrad Rzeszutek Wilk
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=1333410186.1270.92.camel@sbsiddha-desk.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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

all inboxes | Powered by JetHome®