From: Rene Herman <rene.herman@keyaccess.nl>
To: trenn@suse.de
Cc: Shaohua Li <shaohua.li@intel.com>,
Dave Young <hidave.darkstar@gmail.com>,
lenb@kernel.org, linux-acpi@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Zhao Yakui <yakui.zhao@intel.com>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] Set pnp_init_resource_table, pnp_resource_change, pnp_manual_config_dev deprecated
Date: Fri, 30 Nov 2007 18:27:39 +0100 [thread overview]
Message-ID: <4750480B.9010909@keyaccess.nl> (raw)
In-Reply-To: <1196417657.23251.293.camel@queen.suse.de>
On 30-11-07 11:14, Thomas Renninger wrote:
> This should be 2.6.24 material:
>
> Mark pnp_init_resource_table, pnp_resource_change, pnp_manual_config_dev deprecated
>
> Thanks to Rene Herman, the remaining calls to those functions got eliminated
> in the sound/isa layer recently.
> Those functions are a workaround for wrong BIOS pnp information and give
> drivers the possibility to override BIOS exported PNP resources.
> This can be done through sysfs since 2.6, therefore these functions should
> vanish rather soon, as dynamic allocation for PNP resources is depending
> on it.
I'll withhold an ack on this for now. The ALSA side patch has hit the ALSA
repositories but wouldn't seem likely to end up in 2.6.24 at this point in
the development cycle.
Can't have it deprecated with ALSA still using them...
Rene.
next prev parent reply other threads:[~2007-11-30 17:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 9:11 pnpacpi : exceeded the max number of IO resources 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
2007-11-30 10:14 ` [PATCH] Set pnp_init_resource_table, pnp_resource_change, pnp_manual_config_dev deprecated Thomas Renninger
2007-11-30 17:27 ` Rene Herman [this message]
2008-01-16 21:56 ` Len Brown
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=4750480B.9010909@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bjorn.helgaas@hp.com \
--cc=hidave.darkstar@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--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).