linux-kernel - Re: [char-misc-next 08/11] mei: nfc: Initial nfc 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: <201302072226.42375.arnd@arndb.de>
Date:	Thu, 7 Feb 2013 22:26:42 +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 08/11] mei: nfc: Initial nfc implementation

On Thursday 07 February 2013, Tomas Winkler wrote:
> 
> From: Samuel Ortiz <sameo@...ux.intel.com>
> 
> NFC ME client is exported through mei bus to be consumed by the
> NFC subsystem.
> 
> NFC is represented by two mei clients: An info one and the actual
> NFC one. In order for correct connection we first need to retrieve the
> firmware information from the info client.
> 
> Signed-off-by: Samuel Ortiz <sameo@...ux.intel.com>
> Signed-off-by: Tomas Winkler <tomas.winkler@...el.com>

Shouldn't this be moved to the drivers/nfc directory? Generally speaking,
all drivers nowadays tend to live in the directories of the subsystems
they are implementing support for, not the subsystems that they are
implemented with.

	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/