From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Subject: Re: [PATCH] i2c: reorganize muxes to a standard pattern
Date: Mon, 21 Nov 2011 13:52:43 +0100 [thread overview]
Message-ID: <20111121125243.GA4768@pengutronix.de> (raw)
In-Reply-To: <1321220474-11378-1-git-send-email-w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 3503 bytes --]
On Sun, Nov 13, 2011 at 10:41:14PM +0100, Wolfram Sang wrote:
> Analog to ca632f5 (spi: reorganize drivers), introduce a standard pattern
> for naming the muxes. This is done for the rest of the I2C subsystem already, so
> we stay in sync with that.
>
> Signed-off-by: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
> ---
Ping.
>
> Only build tested.
>
> drivers/i2c/muxes/Kconfig | 9 ---------
> drivers/i2c/muxes/Makefile | 6 +++---
> .../i2c/muxes/{gpio-i2cmux.c => i2c-mux-gpio.c} | 0
> drivers/i2c/muxes/{pca9541.c => i2c-mux-pca9541.c} | 0
> drivers/i2c/muxes/{pca954x.c => i2c-mux-pca954x.c} | 0
> 5 files changed, 3 insertions(+), 12 deletions(-)
> rename drivers/i2c/muxes/{gpio-i2cmux.c => i2c-mux-gpio.c} (100%)
> rename drivers/i2c/muxes/{pca9541.c => i2c-mux-pca9541.c} (100%)
> rename drivers/i2c/muxes/{pca954x.c => i2c-mux-pca954x.c} (100%)
>
> diff --git a/drivers/i2c/muxes/Kconfig b/drivers/i2c/muxes/Kconfig
> index 90b7a01..a112d9d 100644
> --- a/drivers/i2c/muxes/Kconfig
> +++ b/drivers/i2c/muxes/Kconfig
> @@ -14,9 +14,6 @@ config I2C_MUX_GPIO
> I2C busses connected through a MUX, which is controlled
> through GPIO pins.
>
> - This driver can also be built as a module. If so, the module
> - will be called gpio-i2cmux.
> -
> config I2C_MUX_PCA9541
> tristate "NXP PCA9541 I2C Master Selector"
> depends on EXPERIMENTAL
> @@ -24,9 +21,6 @@ config I2C_MUX_PCA9541
> If you say yes here you get support for the NXP PCA9541
> I2C Master Selector.
>
> - This driver can also be built as a module. If so, the module
> - will be called pca9541.
> -
> config I2C_MUX_PCA954x
> tristate "Philips PCA954x I2C Mux/switches"
> depends on EXPERIMENTAL
> @@ -34,7 +28,4 @@ config I2C_MUX_PCA954x
> If you say yes here you get support for the Philips PCA954x
> I2C mux/switch devices.
>
> - This driver can also be built as a module. If so, the module
> - will be called pca954x.
> -
> endmenu
> diff --git a/drivers/i2c/muxes/Makefile b/drivers/i2c/muxes/Makefile
> index 4640436..5826249 100644
> --- a/drivers/i2c/muxes/Makefile
> +++ b/drivers/i2c/muxes/Makefile
> @@ -1,8 +1,8 @@
> #
> # Makefile for multiplexer I2C chip drivers.
>
> -obj-$(CONFIG_I2C_MUX_GPIO) += gpio-i2cmux.o
> -obj-$(CONFIG_I2C_MUX_PCA9541) += pca9541.o
> -obj-$(CONFIG_I2C_MUX_PCA954x) += pca954x.o
> +obj-$(CONFIG_I2C_MUX_GPIO) += i2c-mux-gpio.o
> +obj-$(CONFIG_I2C_MUX_PCA9541) += i2c-mux-pca9541.o
> +obj-$(CONFIG_I2C_MUX_PCA954x) += i2c-mux-pca954x.o
>
> ccflags-$(CONFIG_I2C_DEBUG_BUS) := -DDEBUG
> diff --git a/drivers/i2c/muxes/gpio-i2cmux.c b/drivers/i2c/muxes/i2c-mux-gpio.c
> similarity index 100%
> rename from drivers/i2c/muxes/gpio-i2cmux.c
> rename to drivers/i2c/muxes/i2c-mux-gpio.c
> diff --git a/drivers/i2c/muxes/pca9541.c b/drivers/i2c/muxes/i2c-mux-pca9541.c
> similarity index 100%
> rename from drivers/i2c/muxes/pca9541.c
> rename to drivers/i2c/muxes/i2c-mux-pca9541.c
> diff --git a/drivers/i2c/muxes/pca954x.c b/drivers/i2c/muxes/i2c-mux-pca954x.c
> similarity index 100%
> rename from drivers/i2c/muxes/pca954x.c
> rename to drivers/i2c/muxes/i2c-mux-pca954x.c
> --
> 1.7.2.5
>
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-11-21 12:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 21:41 [PATCH] i2c: reorganize muxes to a standard pattern Wolfram Sang
[not found] ` <1321220474-11378-1-git-send-email-w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-11-21 12:52 ` Wolfram Sang [this message]
2011-11-27 20:48 ` Jean Delvare
[not found] ` <20111127214847.547542fb-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-11-27 21:15 ` Peter Korsgaard
[not found] ` <87sjl9gtcv.fsf-uXGAPMMVk8amE9MCos8gUmSdvHPH+/yF@public.gmane.org>
2011-11-28 8:22 ` Jean Delvare
[not found] ` <20111128092227.3d5d6a25-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-11-28 9:38 ` Wolfram Sang
[not found] ` <20111128093835.GA4243-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-11-28 9:58 ` Peter Korsgaard
[not found] ` <874nxoh8l5.fsf-uXGAPMMVk8amE9MCos8gUmSdvHPH+/yF@public.gmane.org>
2011-11-28 11:57 ` Jean Delvare
[not found] ` <20111128125751.3d6a3ca7-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2012-01-07 14:38 ` Jean Delvare
[not found] ` <20120107153820.45ed4b37-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2012-01-07 14:46 ` Wolfram Sang
[not found] ` <20120107144559.GA2537-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-01-07 14:51 ` Jean Delvare
2012-03-31 6:21 ` Jean Delvare
[not found] ` <20120331082112.2fcc13c3-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2012-03-31 6:56 ` Wolfram Sang
[not found] ` <20120331065641.GA9211-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-03-31 9:18 ` Peter Korsgaard
2011-11-27 22:04 ` Guenter Roeck
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=20111121125243.GA4768@pengutronix.de \
--to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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).