From: Greg KH <greg@kroah.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Michael Hennerich <hennerich@blackfin.uclinux.org>,
Anantha Narayanan <Anantha.Narayanan@intel.com>,
Samu Onkalo <samu.p.onkalo@nokia.com>,
Hemanth V <hemanthv@ti.com>,
Christoph Mair <christoph.mair@gmail.com>,
Grant Likely <grant.likely@secretlab.ca>,
Ben Gardner <bgardner@wabtec.com>,
Minkyu Kang <mk7.kang@samsung.com>,
Kalhan Trisal <kalhan.trisal@intel.com>,
"Darrick J. Wong" <djwong@us.ibm.com>,
Daniel Mack <zonque@gmail.com>,
Rodolfo Giometti <giometti@linux.it>,
Arnd Bergmann <arnd@arndb.de>,
Eric Piel <eric.piel@tremplin-utc.net>,
Anatolij Gustschin <agust@denx.de>
Subject: Re: [PATCH 1/2] MISC: convert drivers/misc/* to use module_i2c_driver()
Date: Sat, 26 Nov 2011 20:16:42 -0800 [thread overview]
Message-ID: <20111127041642.GA16385@kroah.com> (raw)
In-Reply-To: <1322194447.30842.0.camel@phoenix>
On Fri, Nov 25, 2011 at 12:14:07PM +0800, 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.
Can you hang on to these patches until after 3.3-rc1 is out and the
macros are in Linus's tree? That way the cross-tree dependancy will not
be there and all of the individual subsystem maintainers can apply
things without having any problems.
thanks,
greg k-h
next prev parent reply other threads:[~2011-11-27 10:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 4:14 [PATCH 1/2] MISC: convert drivers/misc/* to use module_i2c_driver() Axel Lin
2011-11-25 4:16 ` [PATCH 2/2] MISC: convert drivers/misc/* to use module_spi_driver() Axel Lin
2011-11-25 7:51 ` Michael Hennerich
2011-11-25 8:30 ` [PATCH 1/2] MISC: convert drivers/misc/* to use module_i2c_driver() Lars-Peter Clausen
2011-11-25 10:15 ` Arnd Bergmann
2011-11-25 10:40 ` Lars-Peter Clausen
2011-11-25 13:58 ` Arnd Bergmann
2011-11-27 4:16 ` Greg KH [this message]
2011-11-27 12:01 ` Axel Lin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111127041642.GA16385@kroah.com \
--to=greg@kroah.com \
--cc=Anantha.Narayanan@intel.com \
--cc=agust@denx.de \
--cc=arnd@arndb.de \
--cc=axel.lin@gmail.com \
--cc=bgardner@wabtec.com \
--cc=christoph.mair@gmail.com \
--cc=djwong@us.ibm.com \
--cc=eric.piel@tremplin-utc.net \
--cc=giometti@linux.it \
--cc=grant.likely@secretlab.ca \
--cc=hemanthv@ti.com \
--cc=hennerich@blackfin.uclinux.org \
--cc=kalhan.trisal@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mk7.kang@samsung.com \
--cc=samu.p.onkalo@nokia.com \
--cc=zonque@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox