From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Shaohua Li <shaohua.li@intel.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
Andrew Morton <akpm@osdl.org>, "Brown, Len" <len.brown@intel.com>,
linux-kernel@vger.kernel.org, ambx1@neo.rr.com,
castet.matthieu@free.fr, linux-acpi@vger.kernel.org,
uwe.bugla@gmx.de
Subject: Re: ACPIPNP and too large IO resources
Date: Sat, 05 Aug 2006 02:19:46 +0200 [thread overview]
Message-ID: <44D3E422.5060805@drzeus.cx> (raw)
In-Reply-To: <1152234189.21189.139.camel@sli10-desk.sh.intel.com>
Shaohua Li wrote:
> Sure. Please merge the patch Bjorn pointed out.
>
So? What's the status of this? Still not in Linus' tree.
Rgds
Pierre
next prev parent reply other threads:[~2006-08-05 0:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 6:47 ACPIPNP and too large IO resources Pierre Ossman
2006-07-05 16:47 ` Bjorn Helgaas
2006-07-05 20:53 ` Pierre Ossman
2006-07-05 21:36 ` Bjorn Helgaas
2006-07-05 22:18 ` Andrew Morton
2006-07-06 15:29 ` Bjorn Helgaas
2006-07-07 1:03 ` Shaohua Li
2006-08-05 0:19 ` Pierre Ossman [this message]
2006-08-05 1:07 ` 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=44D3E422.5060805@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=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-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=uwe.bugla@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox