linux-kernel - Re: [PATCH v2 0/7] resource, PNPACPI: add bus number and window support

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 for Android: free password hash cracker in your pocket

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

Message-ID: <alpine.LFD.2.00.1003061145260.31447@localhost.localdomain>
Date:	Sat, 6 Mar 2010 11:50:37 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Bjorn Helgaas <bjorn.helgaas@...com>
cc:	Len Brown <lenb@...nel.org>, linux-acpi@...r.kernel.org,
	linux-kernel@...r.kernel.org, Adam Belay <abelay@....edu>
Subject: Re: [PATCH v2 0/7] resource, PNPACPI: add bus number and window
 support

I have nothing against this patch-series, but I'm not really much of a 
pnp person, so I'd like to see this at a minimum being acked by people who 
are, and who would use this. 

In fact, since the primary _reason_ for this seems to be to improve on the 
_CRS parsing code for PCI, I'd have expected that the people involved 
with previous _CRS issues be involved, and perhaps this whole thing could 
go through the PCI tree? But Yinghai Lu and Jesse Barnes weren't even 
cc'd. 

But maybe this really is more of an ACPI issue. I dunno. I get the feeling 
that ACPI doesn't really care, though - the subsystem that actually gets 
_affected_ by all this in the end is PCI.

Anyway, more acks, please. And preferably involve the PCI people too.

			Linus
--
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/