From: Greg KH <greg@kroah.com>
To: Andreas Herrmann <andreas.herrmann3@amd.com>
Cc: stable@kernel.org, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [stable] [PATCH 0/2] x86: check correctness of IRQ0 override on systems with ATI/AMD SB450/SB600 chipsets
Date: Thu, 16 Oct 2008 10:46:14 -0700 [thread overview]
Message-ID: <20081016174614.GA11120@kroah.com> (raw)
In-Reply-To: <20081016120615.GE29183@alberich.amd.com>
On Thu, Oct 16, 2008 at 02:06:15PM +0200, Andreas Herrmann wrote:
> On Wed, Oct 15, 2008 at 12:17:20PM -0700, Greg KH wrote:
> > On Wed, Oct 15, 2008 at 12:41:18PM +0200, Andreas Herrmann wrote:
> > > Hi,
> > >
> > > following patches should go into 2.6.27-stable tree.
> > >
> > > They fix issues with HP Laptops that provide a wrong override for IRQ0
> > > and which change the thermal trip point as soon as Linux unmasks
> > > IOAPIC INT2.
> >
> > Are these patches in the upstream Linus kernel already?
> >
> > If so, can you please give us the git commit ids?
>
> The one for SB450 is upstream. It's commit
> 33fb0e4eb53f16af312f9698f974e2e64af39c12
That one is already added to the tree.
> The second one was posted yesterday and it is not yet commited.
Please let us know when it makes it upstream.
> BTW, I just posted another patch to remove superfluos DMI-quirks
> that are related to HP Laptops with SB450/SB600.
> IMHO this patch should go into stable as well. But first I'd like
> to get a response from Ingo here.
Sure, just let us know when it goes upstream if you want it in -stable.
thanks,
greg k-h
next prev parent reply other threads:[~2008-10-16 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 10:41 [PATCH 0/2][stable] x86: check correctness of IRQ0 override on systems with ATI/AMD SB450/SB600 chipsets Andreas Herrmann
2008-10-15 19:17 ` [stable] [PATCH 0/2] " Greg KH
2008-10-16 12:06 ` Andreas Herrmann
2008-10-16 17:46 ` Greg KH [this message]
2008-10-23 20:33 ` Greg KH
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=20081016174614.GA11120@kroah.com \
--to=greg@kroah.com \
--cc=andreas.herrmann3@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stable@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 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.