From: Rene Herman <rene.herman@keyaccess.nl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Young <hidave.darkstar@gmail.com>,
Frans Pop <elendil@planet.nl>,
bjorn.helgaas@hp.com, Len Brown <lenb@kernel.org>,
akpm@osdl.org, cholvenstot@comcast.net,
linux-kernel@vger.kernel.org, shaohua.li@intel.com,
trenn@suse.de, yakui.zhao@intel.com
Subject: Re: pnpacpi : exceeded the max number of IO resources
Date: Wed, 16 Jan 2008 14:04:18 +0100 [thread overview]
Message-ID: <478E00D2.50908@keyaccess.nl> (raw)
In-Reply-To: <478DB9B4.1030107@keyaccess.nl>
On 16-01-08 09:00, Rene Herman wrote:
> On 16-01-08 06:55, Dave Young wrote:
>
>> I noticed the port number changed to 40 in 2.6.24-rc8, but it's not
>> enough for me still.
>
> Yes, that's known. In .23 even more were (silently) ignored though.
> Since .24-rc8 you should at least get just 1 warning (per resource type)
Assuming, that is, that Linus would've applied Len's trivial fix here:
http://lkml.org/lkml/2008/1/14/251
> and if all's well .25 should kill the static limit completely.
Rene.
next prev parent reply other threads:[~2008-01-16 13:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 13:14 pnpacpi : exceeded the max number of IO resources Chris Holvenstot
2007-11-30 22:22 ` Rene Herman
2007-12-03 17:02 ` Rene Herman
2007-12-03 22:51 ` Chris Holvenstot
2007-12-04 0:55 ` Shaohua Li
2007-12-04 1:15 ` Dave Young
2007-12-05 20:39 ` Bjorn Helgaas
2007-12-19 3:07 ` Valdis.Kletnieks
2008-01-09 3:50 ` Len Brown
2008-01-09 9:34 ` Frans Pop
2008-01-09 14:47 ` Rene Herman
2008-01-16 5:55 ` Dave Young
2008-01-16 8:00 ` Rene Herman
2008-01-16 13:04 ` Rene Herman [this message]
2008-01-19 11:03 ` Frans Pop
2008-01-19 18:38 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2007-11-29 9:11 Dave Young
2007-11-30 1:18 ` Dave Young
2007-11-30 2:21 ` Zhao Yakui
2007-11-30 6:40 ` Valdis.Kletnieks
2007-11-30 8:14 ` Zhao Yakui
2007-11-30 2:18 ` Rene Herman
2007-11-30 2:32 ` Shaohua Li
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=478E00D2.50908@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=cholvenstot@comcast.net \
--cc=elendil@planet.nl \
--cc=hidave.darkstar@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=trenn@suse.de \
--cc=yakui.zhao@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;
as well as URLs for NNTP newsgroup(s).