From: Andrew Morton <akpm@osdl.org>
To: "Brown, Len" <len.brown@intel.com>
Cc: bjorn.helgaas@hp.com, ambx1@neo.rr.com, castet.matthieu@free.fr,
shaohua.li@intel.com, linux-acpi@vger.kernel.org,
rmk+serial@arm.linux.org.uk, linux-serial@vger.kernel.org
Subject: Re: [PATCH 1/2] PNPACPI: support shareable interrupts
Date: Fri, 30 Jun 2006 18:14:31 -0700 [thread overview]
Message-ID: <20060630181431.6245202c.akpm@osdl.org> (raw)
In-Reply-To: <CFF307C98FEABE47A452B27C06B85BB6E16DA1@hdsmsx411.amr.corp.intel.com>
"Brown, Len" <len.brown@intel.com> wrote:
>
> >pnpacpi confuses me. Who maintains it? Is it considered an
> >APCI thing, or a PNP thing or a Bjorn thing?
>
> PNP is Adam's generic Linux PNP layer.
> It has "drivers" underneath is, such as pnp-isa, and pnp-bios
>
> Shaohua invented pnp-acpi as a driver to replace pnp-bios
> on ACPI-enabled systems.
>
> So PNPACPI is the connection between ACPI and PNP,
> and folks who conribute to either might contribute to it.
> Most of the issues with it to date have been ACPI-specific,
> rather than PNP-specific, including this one.
>
> Bjorn, of course, is qualified to contribute to just about
> any part of the kernel. So a "Bjorn thing" could be just
> about anything;-)
>
OK. But that still didn't give me a how-to-get-this-to-mainline graph.
Bjorn, are these patches considered for-2.6.18 material? (They look like
it).
next prev parent reply other threads:[~2006-07-01 1:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-01 0:59 [PATCH 1/2] PNPACPI: support shareable interrupts Brown, Len
2006-07-01 1:14 ` Andrew Morton [this message]
2006-07-01 3:50 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2006-06-30 18:58 Bjorn Helgaas
2006-06-30 23:02 ` Andrew Morton
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=20060630181431.6245202c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ambx1@neo.rr.com \
--cc=bjorn.helgaas@hp.com \
--cc=castet.matthieu@free.fr \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rmk+serial@arm.linux.org.uk \
--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