public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-mmc@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Subject: Re: [PATCH/RFC 1/4] mmc: renesas_sdhi: rename sh_mobile_sdhi as renesas_sdhi
Date: Wed, 22 Jun 2016 16:11:10 +0200	[thread overview]
Message-ID: <20160622141110.GA1645@katana> (raw)
In-Reply-To: <1465963317-28672-2-git-send-email-horms+renesas@verge.net.au>

[-- Attachment #1: Type: text/plain, Size: 2422 bytes --]

On Wed, Jun 15, 2016 at 01:01:54PM +0900, Simon Horman wrote:
> The SDHI driver is applicable to a wider range of SoCs than SH-Mobile,
> Renesas seems to be a more appropriate name.
> 
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>

It feels strange to rename the file and leaving all the naming inside
the file still 'sh_mobile_*'. On the other hand, renaming all those,
too, is intrusive, so I wonder if we can't keep the filename "for
historic reasons"?

> ---
>  drivers/mmc/host/Kconfig                              | 4 ++--
>  drivers/mmc/host/Makefile                             | 2 +-
>  drivers/mmc/host/{sh_mobile_sdhi.c => renesas_sdhi.c} | 0
>  3 files changed, 3 insertions(+), 3 deletions(-)
>  rename drivers/mmc/host/{sh_mobile_sdhi.c => renesas_sdhi.c} (100%)
> 
> diff --git a/drivers/mmc/host/Kconfig b/drivers/mmc/host/Kconfig
> index 0aa484c10c0a..840b17150263 100644
> --- a/drivers/mmc/host/Kconfig
> +++ b/drivers/mmc/host/Kconfig
> @@ -560,13 +560,13 @@ config MMC_TMIO
>  	  T7L66XB and also HTC ASIC3
>  
>  config MMC_SDHI
> -	tristate "SH-Mobile SDHI SD/SDIO controller support"
> +	tristate "Renesas SDHI SD/SDIO controller support"
>  	depends on SUPERH || ARM || ARM64
>  	depends on SUPERH || ARCH_RENESAS || COMPILE_TEST
>  	select MMC_TMIO_CORE
>  	help
>  	  This provides support for the SDHI SD/SDIO controller found in
> -	  SuperH and ARM SH-Mobile SoCs
> +	  SuperH, and Renesas ARM and arm64 based SoCs.
>  
>  config MMC_CB710
>  	tristate "ENE CB710 MMC/SD Interface support"
> diff --git a/drivers/mmc/host/Makefile b/drivers/mmc/host/Makefile
> index af918d261ff9..206233218781 100644
> --- a/drivers/mmc/host/Makefile
> +++ b/drivers/mmc/host/Makefile
> @@ -38,7 +38,7 @@ obj-$(CONFIG_MMC_TMIO)		+= tmio_mmc.o
>  obj-$(CONFIG_MMC_TMIO_CORE)	+= tmio_mmc_core.o
>  tmio_mmc_core-y			:= tmio_mmc_pio.o
>  tmio_mmc_core-$(subst m,y,$(CONFIG_MMC_SDHI))	+= tmio_mmc_dma.o
> -obj-$(CONFIG_MMC_SDHI)		+= sh_mobile_sdhi.o
> +obj-$(CONFIG_MMC_SDHI)		+= renesas_sdhi.o
>  obj-$(CONFIG_MMC_CB710)		+= cb710-mmc.o
>  obj-$(CONFIG_MMC_VIA_SDMMC)	+= via-sdmmc.o
>  obj-$(CONFIG_SDH_BFIN)		+= bfin_sdh.o
> diff --git a/drivers/mmc/host/sh_mobile_sdhi.c b/drivers/mmc/host/renesas_sdhi.c
> similarity index 100%
> rename from drivers/mmc/host/sh_mobile_sdhi.c
> rename to drivers/mmc/host/renesas_sdhi.c
> -- 
> 2.1.4
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-06-22 14:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15  4:01 [PATCH/RFC 0/4] mmc: renesas_sdhi: add R-Car Gen-3 DMA support Simon Horman
2016-06-15  4:01 ` [PATCH/RFC 1/4] mmc: renesas_sdhi: rename sh_mobile_sdhi as renesas_sdhi Simon Horman
2016-06-22 14:11   ` Wolfram Sang [this message]
2016-06-15  4:01 ` [PATCH/RFC 2/4] mmc: renesas_sdhi, tmio: make dma more modular Simon Horman
2016-06-22 14:13   ` Wolfram Sang
2016-06-15  4:01 ` [PATCH/RFC 3/4] mmc: renesas_sdhi: rename DMA source file as renesas_sdhi_dma.c Simon Horman
2016-06-22 14:21   ` Wolfram Sang
2016-06-15  4:01 ` [PATCH/RFC 4/4] mmc: renesas_sdhi: add support for R-Car Gen3 SDHI DMAC Simon Horman
2016-06-27 12:18   ` Wolfram Sang
2016-06-27 12:17 ` [PATCH/RFC 0/4] mmc: renesas_sdhi: add R-Car Gen-3 DMA support Wolfram Sang

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=20160622141110.GA1645@katana \
    --to=wsa@the-dreams.de \
    --cc=horms+renesas@verge.net.au \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=ulf.hansson@linaro.org \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=yoshihiro.shimoda.uh@renesas.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