From: Jean Delvare <khali@linux-fr.org>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Axel Lin <axel.lin@gmail.com>,
linux-kernel@vger.kernel.org, Ben Dooks <ben-linux@fluff.org>,
Jochen Friedrich <jochen@scram.de>,
Peter Korsgaard <jacmet@sunsite.dk>,
Guan Xuetao <gxt@mprc.pku.edu.cn>,
Manuel Lauss <manuel.lauss@googlemail.com>,
Barry Song <21cnbao@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Yong Zhang <yong.zhang0@gmail.com>,
Lucas De Marchi <lucas.demarchi@profusion.mobi>,
Grant Likely <grant.likely@secretlab.ca>,
Samuel Ortiz <sameo@linux.intel.com>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: convert drivers/i2c/* to use module_platform_driver()
Date: Sun, 27 Nov 2011 20:50:28 +0100 [thread overview]
Message-ID: <20111127205028.708ea59f@endymion.delvare> (raw)
In-Reply-To: <20111127194648.GA26533@pengutronix.de>
On Sun, 27 Nov 2011 20:46:48 +0100, Wolfram Sang wrote:
>
> > > -module_init(gpiomux_init);
> > > -module_exit(gpiomux_exit);
> > > +module_platform_driver(gpiomux_driver);
> >
> > This one would be better as a separate patch, as it touches a different
> > subdirectory, which I am responsible for.
>
> ... which has a patch pending[1], hint ;)
>
> [1] http://comments.gmane.org/gmane.linux.drivers.i2c/9432
Yes, that's one of the reasons why I think a separate patch would be
more appropriate. It might be difficult to avoid patch collisions
otherwise.
--
Jean Delvare
next prev parent reply other threads:[~2011-11-27 19:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-27 6:12 [PATCH] i2c: convert drivers/i2c/* to use module_platform_driver() Axel Lin
2011-11-27 8:47 ` Peter Korsgaard
2011-11-27 8:48 ` Wolfram Sang
2011-11-27 13:45 ` Jochen Friedrich
2011-11-27 19:22 ` Jean Delvare
2011-11-27 19:46 ` Wolfram Sang
2011-11-27 19:50 ` Jean Delvare [this message]
2012-01-07 15:00 ` Jean Delvare
2011-11-28 0:56 ` Guan Xuetao
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=20111127205028.708ea59f@endymion.delvare \
--to=khali@linux-fr.org \
--cc=21cnbao@gmail.com \
--cc=axel.lin@gmail.com \
--cc=ben-linux@fluff.org \
--cc=grant.likely@secretlab.ca \
--cc=gxt@mprc.pku.edu.cn \
--cc=jacmet@sunsite.dk \
--cc=jochen@scram.de \
--cc=linus.walleij@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
--cc=manuel.lauss@googlemail.com \
--cc=sameo@linux.intel.com \
--cc=w.sang@pengutronix.de \
--cc=yong.zhang0@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