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]
Date:	Thu, 08 Jan 2009 23:34:49 -0500 (EST)
From:	Len Brown <lenb@...nel.org>
To:	Christoph Hellwig <hch@...radead.org>, Ingo Molnar <mingo@...e.hu>
Cc:	linux-acpi@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 03/15] ACPICA: move common private headers under
 kernel/acpi/acpica/



> On Wed, Jan 07, 2009 at 11:10:17PM +0100, Ingo Molnar wrote:
> > i still tend to regard kernel/* as the core Linux kernel, as code that can 
> > be improved infinitely (only subject to the laws of physics), without 
> > having to worry about how the ACPI spec wants certain things done.

I want to move the Linux-ACPI code and the ACPICA core
out of drivers/ simply because they are not drivers,
and never will be.

The actual ACPI drivers, OTOH, would remain in drivers/acpi/.

So looking around...

arch/ doesn't make sense for something shared by x86 and ia64

firmware/ seems to be about software that doesn't run on the CPU.

kernel/ is evidently sacred ground.                 
 
So I suggest "platform/acpi/" or if we can't imagine any
other cross architecture platform code code that isn't device drivers,
then simply "acpi/"  Would you find that less offensive?

thanks,
Len Brown, Intel Open Source Technology Center

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ