linux-kernel - RE: linux-next: manual merge of the char-misc tree with the ia64 tree

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: <3908561D78D1C84285E8C5FCA982C28F3285CF7A@ORSMSX114.amr.corp.intel.com>
Date:	Tue, 15 Jul 2014 15:22:31 +0000
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Greg KH <greg@...ah.com>, Stephen Rothwell <sfr@...b.auug.org.au>,
	"Borislav Petkov (bp@...en8.de)" <bp@...en8.de>
CC:	Arnd Bergmann <arnd@...db.de>,
	"Chen, Gong" <gong.chen@...ux.intel.com>,
	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andreas Noever <andreas.noever@...il.com>
Subject: RE: linux-next: manual merge of the char-misc tree with the ia64
 tree

> Wait, do we really need a drivers/ras directory for one single driver?
> Why not put it in drivers/misc/ instead?  A whole subdir at the top of
> drivers seems overkill and odd.
>
> As it's a memory driver, what about drivers/firmware/ or drivers/edac/
> or drivers/platform?

It isn't really a firmware driver, and definitely not an EDAC driver.

drivers/platform/x86 seems at least plausible.

Adding Boris as drivers/ras was his idea. I think he has plans
for more stuff to go here.

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