linux-kernel - Re: [char-misc-next 01/11] mei: bus: Initial MEI bus type implementation

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: <201302072229.17591.arnd@arndb.de>
Date:	Thu, 7 Feb 2013 22:29:17 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Tomas Winkler <tomas.winkler@...el.com>
Cc:	gregkh@...uxfoundation.org, sameo@...ux.intel.com,
	linux-kernel@...r.kernel.org
Subject: Re: [char-misc-next 01/11] mei: bus: Initial MEI bus type implementation

On Thursday 07 February 2013, Tomas Winkler wrote:
> From: Samuel Ortiz <sameo@...ux.intel.com>
> 
> mei bus will present some of the me clients
> as devices for other standard subsystems
> 
> Implement the probe, remove, match and the device addtion routines.
> A mei-bus.txt document describing the rationale and the API usage
> is also added.

This looks really nice, but I also think you have reached the point where
you are outgrowing the scope of drivers/misc. How about turning mei
into a top-level subsystem along with this new bus_type?

Another option would be moving it to drivers/bus/mei/ if you don't
want to be quite at the top.

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