linux-kernel - Re: [PATCH 2/3] PNP cleanups - Unify the pnp macros to access resources in the pnp resource table

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: <4742EFBE.6030407@keyaccess.nl>
Date:	Tue, 20 Nov 2007 15:31:26 +0100
From:	Rene Herman <rene.herman@...access.nl>
To:	trenn@...e.de
CC:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Bjorn Helgaas <bjorn.helgaas@...com>,
	"Li, Shaohua" <shaohua.li@...el.com>,
	"yakui.zhao" <yakui.zhao@...el.com>,
	akpm <akpm@...ux-foundation.org>,
	ALSA devel <alsa-devel@...a-project.org>
Subject: Re: [PATCH 2/3] PNP cleanups - Unify the pnp macros to access	resources
 in the pnp resource table

On 20-11-07 15:19, Thomas Renninger wrote:

> At the end is some example code how things could get even more cleaned
> up. It shows how I think pnp layer and one example driver would get
> adjusted. There are not that much drivers making use of
> pnp_resource_change...

The ALSA ISA-PnP drivers do in what I personally consider a bad layering 
violation. Brought up not doing that a while ago on alsa-devel, but no 
discussion ensued. If the PnP maintainer(s) agree with me though, I'd be 
more than happy to rip all of that out of ALSA.

(added alsa-devel)

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/