linux-kernel - Re: [PATCH] Set pnp_init_resource_table, pnp_resource_change, pnp_manual_config

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4750480B.9010909@keyaccess.nl>
Date:	Fri, 30 Nov 2007 18:27:39 +0100
From:	Rene Herman <rene.herman@...access.nl>
To:	trenn@...e.de
CC:	Shaohua Li <shaohua.li@...el.com>,
	Dave Young <hidave.darkstar@...il.com>, lenb@...nel.org,
	linux-acpi@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Zhao Yakui <yakui.zhao@...el.com>,
	Bjorn Helgaas <bjorn.helgaas@...com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH] Set pnp_init_resource_table, pnp_resource_change,	pnp_manual_config_dev
 deprecated

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/