From: Andrew Morton <akpm@linux-foundation.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: ambx1@neo.rr.com, torvalds@linux-foundation.org, abelay@mit.edu,
castet.matthieu@free.fr, shaohua.li@intel.com, lenb@kernel.org,
ThJaeger@gmail.com, Robert.Moore@intel.com,
linux-acpi@vger.kernel.org
Subject: Re: PNPACPI: use _CRS IRQ descriptor length for _SRS, v2
Date: Mon, 9 Jun 2008 15:02:37 -0700 [thread overview]
Message-ID: <20080609150237.92fb06d2.akpm@linux-foundation.org> (raw)
In-Reply-To: <200806091251.56347.bjorn.helgaas@hp.com>
On Mon, 9 Jun 2008 12:51:55 -0600
Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> On Tuesday 27 May 2008 10:53:58 am Bjorn Helgaas wrote:
> > [This fixes a long-standing parport PNPACPI bug (see bugzilla
> > links below). I think it should go in 2.6.26.
> >
> > This v2 patch removes an unnecessary line pointed out by
> > Tom Jaeger.]
>
> This patch is in -mm, but not in 2.6.26-rc5. I'd like suggest
> again that we put it in for 2.6.26 because it fixes parport
> on many machines.
I have it queued under "for 2.6.26, should go via Len's tree". There
are in fact three such patches:
pnpacpi-fix-irq-flag-decoding.patch
pnpacpi-fix-irq-flag-decoding-comment-fix.patch
pnpacpi-fix-shareable-irq-encode-decode.patch
pnpacpi-use-_crs-irq-descriptor-length-for-_srs-v2.patch
Len, what would you prefer happen to these?
I'm planning on doing a maintainer-bombing later in the day.
prev parent reply other threads:[~2008-06-09 22:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 22:29 PNPACPI: use _CRS IRQ descriptor length for _SRS Bjorn Helgaas
2008-05-24 18:55 ` Thomas Jaeger
2008-05-27 16:47 ` Bjorn Helgaas
2008-05-27 16:53 ` PNPACPI: use _CRS IRQ descriptor length for _SRS, v2 Bjorn Helgaas
2008-06-09 18:51 ` Bjorn Helgaas
2008-06-09 22:02 ` Andrew Morton [this message]
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=20080609150237.92fb06d2.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Robert.Moore@intel.com \
--cc=ThJaeger@gmail.com \
--cc=abelay@mit.edu \
--cc=ambx1@neo.rr.com \
--cc=bjorn.helgaas@hp.com \
--cc=castet.matthieu@free.fr \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=torvalds@linux-foundation.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 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.