From: Andi Kleen <andi@firstfloor.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Andi Kleen <andi@firstfloor.org>, Adam M Belay <abelay@mit.edu>,
Matthieu CASTET <matthieu.castet@parrot.com>,
Li Shaohua <shaohua.li@intel.com>,
linux-acpi@vger.kernel.org, Len Brown <lenb@kernel.org>
Subject: Re: [patch] PNPACPI: ignore the producer/consumer bit for extended IRQ descriptors
Date: Mon, 25 Aug 2008 12:15:43 +0200 [thread overview]
Message-ID: <20080825101543.GC26610@one.firstfloor.org> (raw)
In-Reply-To: <200808220947.18253.bjorn.helgaas@hp.com>
On Fri, Aug 22, 2008 at 09:47:17AM -0600, Bjorn Helgaas wrote:
> The Extended Interrupt descriptor has a producer/consumer bit, but
> it's not clear what that would mean, and existing BIOSes use the bit
> inconsistently. This patch makes Linux PNPACPI ignore the bit.
Added thanks. Will put in the next 2.6.27 update.
-Andi
next prev parent reply other threads:[~2008-08-25 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 15:47 [patch] PNPACPI: ignore the producer/consumer bit for extended IRQ descriptors Bjorn Helgaas
2008-08-25 10:15 ` Andi Kleen [this message]
2008-08-25 14:56 ` Bjorn Helgaas
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=20080825101543.GC26610@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=abelay@mit.edu \
--cc=bjorn.helgaas@hp.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=matthieu.castet@parrot.com \
--cc=shaohua.li@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