From: Jean Delvare <khali@linux-fr.org>
To: Ben Dooks <ben-i2c@fluff.org>,
Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
Linus Walleij <linus.walleij@stericsson.com>,
Wolfram Sang <w.sang@pengutronix.de>,
Ralf Baechle <ralf@linux-mips.org>,
srinidhi kasagar <srinidhi.kasagar@stericsson.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
qi.wang@intel.com, andrew.chih.howe.khor@intel.com,
yong.y.wang@intel.com, kok.howg.ewe@intel.com
Subject: Re: [PATCH] EG20T: Update PCH_I2C driver to 2.6.36
Date: Mon, 6 Dec 2010 08:53:04 +0100 [thread overview]
Message-ID: <20101206085304.094d1078@endymion.delvare> (raw)
In-Reply-To: <4CFC6622.1050006@fluff.org>
On Mon, 06 Dec 2010 04:27:14 +0000, Ben Dooks wrote:
> On 09/11/10 04:25, Tomoya MORINAGA wrote:
> > diff --git a/drivers/i2c/busses/Makefile b/drivers/i2c/busses/Makefile
> > index c3ef492..e55e051 100644
> > --- a/drivers/i2c/busses/Makefile
> > +++ b/drivers/i2c/busses/Makefile
> > @@ -60,6 +60,7 @@ obj-$(CONFIG_I2C_STU300) += i2c-stu300.o
> > obj-$(CONFIG_I2C_VERSATILE) += i2c-versatile.o
> > obj-$(CONFIG_I2C_OCTEON) += i2c-octeon.o
> > obj-$(CONFIG_I2C_XILINX) += i2c-xiic.o
> > +obj-$(CONFIG_I2C_EG20T) += i2c-eg20t.o
>
> Jean, do you want these alphabetically sorted?
I prefer them sorted alphabetically, yes. For several reasons:
* Makes it easier to find out a specific entry.
* Makes it easier to spot duplicate drivers or drivers for very similar
devices which could be merged.
* Limits the risks of reject when two new drivers are added in parallel.
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2010-12-06 7:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 4:25 Tomoya MORINAGA
2010-11-09 5:21 ` Wang, Qi
2010-11-09 8:29 ` Jean Delvare
2010-11-09 9:50 ` Ben Dooks
2010-11-30 1:39 ` Wang, Qi
2010-12-06 4:27 ` Ben Dooks
2010-12-06 7:53 ` Jean Delvare [this message]
2010-12-07 1:38 ` Tomoya MORINAGA
2010-12-06 4:41 ` Ben Dooks
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=20101206085304.094d1078@endymion.delvare \
--to=khali@linux-fr.org \
--cc=andrew.chih.howe.khor@intel.com \
--cc=ben-i2c@fluff.org \
--cc=kok.howg.ewe@intel.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qi.wang@intel.com \
--cc=ralf@linux-mips.org \
--cc=sameo@linux.intel.com \
--cc=srinidhi.kasagar@stericsson.com \
--cc=tomoya-linux@dsn.okisemi.com \
--cc=w.sang@pengutronix.de \
--cc=yong.y.wang@intel.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
all inboxes | Powered by JetHome®