linux-kernel - Re: [PATCH 1/2] MISC: convert drivers/misc/* to use module_i2c

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: <4ECF5213.20501@metafoo.de>
Date:	Fri, 25 Nov 2011 09:30:11 +0100
From:	Lars-Peter Clausen <lars@...afoo.de>
To:	Axel Lin <axel.lin@...il.com>
CC:	linux-kernel@...r.kernel.org,
	Michael Hennerich <hennerich@...ckfin.uclinux.org>,
	Anantha Narayanan <Anantha.Narayanan@...el.com>,
	Samu Onkalo <samu.p.onkalo@...ia.com>,
	Hemanth V <hemanthv@...com>,
	Christoph Mair <christoph.mair@...il.com>,
	Grant Likely <grant.likely@...retlab.ca>,
	Ben Gardner <bgardner@...tec.com>,
	Minkyu Kang <mk7.kang@...sung.com>,
	Kalhan Trisal <kalhan.trisal@...el.com>,
	"Darrick J. Wong" <djwong@...ibm.com>,
	Daniel Mack <zonque@...il.com>,
	Rodolfo Giometti <giometti@...ux.it>,
	Arnd Bergmann <arnd@...db.de>,
	Greg Kroah-Hartman <greg@...ah.com>,
	Eric Piel <eric.piel@...mplin-utc.net>,
	Anatolij Gustschin <agust@...x.de>
Subject: Re: [PATCH 1/2] MISC: convert drivers/misc/* to use module_i2c_driver()

On 11/25/2011 05:14 AM, Axel Lin wrote:
> This patch converts the drivers in drivers/misc/* to use the
> module_i2c_driver() macro which makes the code smaller and a bit
> simpler.
> 

I think we should wait with spi and i2c patches until the macro can actually
be found in respective subsystem tree. Or do you want these patches to go
through GregKH's driver-core tree?
--
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/