u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Prafulla Wadaskar <prafulla@marvell.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V3 2/4] i2c: rename kirkwood_i2c to mvtwsi
Date: Fri, 27 Aug 2010 05:17:51 -0700	[thread overview]
Message-ID: <F766E4F80769BD478052FB6533FA745D19A680404B@SC-VEXCH4.marvell.com> (raw)
In-Reply-To: <1282889535-27228-3-git-send-email-albert.aribaud@free.fr>

 

> -----Original Message-----
> From: u-boot-bounces at lists.denx.de 
> [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Albert Aribaud
> Sent: Friday, August 27, 2010 11:42 AM
> To: u-boot at lists.denx.de
> Subject: [U-Boot] [PATCH V3 2/4] i2c: rename kirkwood_i2c to mvtwsi
> 
> This driver is not kirkwood-specific and can also be used
> e.g. by orion5x. Rename to a SoC-neutral name.
> 
> Signed-off-by: Albert Aribaud <albert.aribaud@free.fr>
> ---
>  drivers/i2c/Makefile                     |    2 +-
>  drivers/i2c/{kirkwood_i2c.c => mvtwsi.c} |    0
>  2 files changed, 1 insertions(+), 1 deletions(-)
>  rename drivers/i2c/{kirkwood_i2c.c => mvtwsi.c} (100%)
> 
> diff --git a/drivers/i2c/Makefile b/drivers/i2c/Makefile
> index d2c2515..ae04d53 100644
> --- a/drivers/i2c/Makefile
> +++ b/drivers/i2c/Makefile
> @@ -28,7 +28,7 @@ LIB	:= $(obj)libi2c.a
>  COBJS-$(CONFIG_BFIN_TWI_I2C) += bfin-twi_i2c.o
>  COBJS-$(CONFIG_DRIVER_DAVINCI_I2C) += davinci_i2c.o
>  COBJS-$(CONFIG_FSL_I2C) += fsl_i2c.o
> -COBJS-$(CONFIG_I2C_KIRKWOOD) += kirkwood_i2c.o
> +COBJS-$(CONFIG_I2C_DRIVER_MVTWSI) += mvtwsi.o

This makefile needs separate spin for cleanup
But I think _DRIVER_ can be removed here to make it short at this moment

Regards..
Prafulla ..
 
>  COBJS-$(CONFIG_I2C_MXC) += mxc_i2c.o
>  COBJS-$(CONFIG_DRIVER_OMAP1510_I2C) += omap1510_i2c.o
>  COBJS-$(CONFIG_DRIVER_OMAP24XX_I2C) += omap24xx_i2c.o
> diff --git a/drivers/i2c/kirkwood_i2c.c b/drivers/i2c/mvtwsi.c
> similarity index 100%
> rename from drivers/i2c/kirkwood_i2c.c
> rename to drivers/i2c/mvtwsi.c
> -- 
> 1.7.1
> 
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
> 

  reply	other threads:[~2010-08-27 12:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-27  6:12 [U-Boot] [PATCH V3 0/4] Improve I2C for orion5x, kirkwood and ED Mini V2 Albert Aribaud
2010-08-27  6:12 ` [U-Boot] [PATCH V3 1/4] suen3: remove CONFIG_HARD_I2C and related defines Albert Aribaud
2010-08-27  6:12 ` [U-Boot] [PATCH V3 2/4] i2c: rename kirkwood_i2c to mvtwsi Albert Aribaud
2010-08-27 12:17   ` Prafulla Wadaskar [this message]
2010-08-27  6:12 ` [U-Boot] [PATCH V3 3/4] i2c: rewrite mvtwsi, support orion5x and kirkwood Albert Aribaud
2010-08-27 12:34   ` Prafulla Wadaskar
2010-08-27 13:03     ` Albert ARIBAUD
2010-08-27 14:30       ` Prafulla Wadaskar
2010-08-27 14:45         ` Albert ARIBAUD
2010-08-27  6:12 ` [U-Boot] [PATCH V3 4/4] edminiv2: add I2C support using mvtwsi driver Albert Aribaud
2010-08-27 12:20   ` Prafulla Wadaskar
2010-08-27 13:42     ` Albert ARIBAUD

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=F766E4F80769BD478052FB6533FA745D19A680404B@SC-VEXCH4.marvell.com \
    --to=prafulla@marvell.com \
    --cc=u-boot@lists.denx.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).