From: Jean Delvare <khali@linux-fr.org>
To: "Amaury Decrême" <amaury.decreme@gmail.com>
Cc: ben-linux@fluff.org, w.sang@pengutronix.de, rob@landley.net,
jeffrey.t.kirsher@intel.com, akpm@linux-foundation.org,
davem@davemloft.net, gregkh@linuxfoundation.org, joe@perches.com,
ralf@linux-mips.org, dirk.brandewie@gmail.com,
jayachandranc@netlogicmicro.com, linux-i2c@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] I2C: SIS964: Bus driver
Date: Fri, 3 Aug 2012 19:07:58 +0200 [thread overview]
Message-ID: <20120803190758.34e67b1e@endymion.delvare> (raw)
In-Reply-To: <CAPXEm73QX7haU5p7HU+=+qo5wnivt6j+WH5bQGZ0ZK0Ek2Cuyw@mail.gmail.com>
On Fri, 3 Aug 2012 18:36:36 +0200, Amaury Decrême wrote:
> > What is the rationale for not adding support for the new chip to
> > i2c-sis630 then? That would probably be a lot easier to review.
> >
>
> I was afraid that adding SIS964 support to i2c-sis630 would lead
> to confusion.
There's nothing confusing, drivers supporting several devices are
legion. If the devices are really almost compatible, reusing an
existing driver is the way to go.
> I can try to submit a patch for i2c-sis630. In this case, do you think
> we should keep the 630 name or change it to something else to
> avoid misunderstanding ?
Keep the name. It is very common to name drivers by the name of the
first supported device, and changing a driver name is always a source
of trouble.
--
Jean Delvare
next prev parent reply other threads:[~2012-08-03 17:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 15:35 [PATCH v2 0/2] I2C: SIS964: Bus driver Amaury Decrême
2012-08-03 15:35 ` [PATCH v2 1/2] I2C: SIS964: Bus driver - Driver Amaury Decrême
2012-08-03 15:35 ` [PATCH v2 2/2] I2C: SIS964: Bus driver - other files Amaury Decrême
[not found] ` <1344008145-14579-1-git-send-email-amaury.decreme-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-08-03 16:07 ` [PATCH v2 0/2] I2C: SIS964: Bus driver Jean Delvare
2012-08-03 16:36 ` Amaury Decrême
2012-08-03 17:07 ` Jean Delvare [this message]
2012-08-04 0:38 ` Amaury Decrême
2012-08-05 12:04 ` Jean Delvare
[not found] ` <20120805140454.3e7a9606-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2012-08-05 22:03 ` Amaury Decrême
2012-08-05 22:11 ` [PATCH 0/2] I2C: SIS630: Add SIS964 support Amaury Decrême
2012-08-05 22:11 ` [PATCH 1/2] I2C: SIS630: Add SiS964 support Amaury Decrême
[not found] ` <1344204714-16513-1-git-send-email-amaury.decreme-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-08-05 22:11 ` [PATCH 2/2] I2C: SIS630: Cosmetics Amaury Decrême
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=20120803190758.34e67b1e@endymion.delvare \
--to=khali@linux-fr.org \
--cc=akpm@linux-foundation.org \
--cc=amaury.decreme@gmail.com \
--cc=ben-linux@fluff.org \
--cc=davem@davemloft.net \
--cc=dirk.brandewie@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jayachandranc@netlogicmicro.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=rob@landley.net \
--cc=w.sang@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).