linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@iki.fi>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: spi-devel-general@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: reorganize drivers
Date: Sun, 5 Jun 2011 11:13:31 +0300	[thread overview]
Message-ID: <20110605081331.GA3499@acer> (raw)
In-Reply-To: <20110605071725.26517.11573.stgit@ponder>

On Sun, Jun 05, 2011 at 01:18:14AM -0600, Grant Likely wrote:
> [repost: I had a typo on the spi-devel-general mailing list address]
> 
> Sort the SPI makefile and enforce the naming convention spi_*.c for
> spi drivers.
> 
> This change also rolls the contents of atmel_spi.h into the .c file
> since there is only one user of that particular include file.
> 
> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
> ---
>  drivers/spi/Makefile            |   80 ++++++++-----------
>  drivers/spi/atmel_spi.h         |  167 ---------------------------------------
>  drivers/spi/spi_ath79.c         |    0 
>  drivers/spi/spi_atmel.c         |  155 ++++++++++++++++++++++++++++++++++++
>  drivers/spi/spi_au1550.c        |    0 
>  drivers/spi/spi_coldfire_qspi.c |    0 
>  drivers/spi/spi_davinci.c       |    0 
>  drivers/spi/spi_dw.c            |    2 
>  drivers/spi/spi_dw.h            |    0 
>  drivers/spi/spi_dw_mid.c        |    2 
>  drivers/spi/spi_dw_mmio.c       |    2 
>  drivers/spi/spi_dw_pci.c        |    2 
>  drivers/spi/spi_ep93xx.c        |    0 
>  drivers/spi/spi_mpc512x_psc.c   |    0 
>  drivers/spi/spi_mpc52xx.c       |    0 
>  drivers/spi/spi_mpc52xx_psc.c   |    0 
>  drivers/spi/spi_omap2_mcspi.c   |    0 
>  drivers/spi/spi_omap_100k.c     |    0 
>  drivers/spi/spi_omap_uwire.c    |    0 
>  drivers/spi/spi_orion.c         |    0 
>  drivers/spi/spi_pl022.c         |    0 
>  drivers/spi/spi_pxa2xx.c        |    0 
>  drivers/spi/spi_pxa2xx_pci.c    |    0 
>  drivers/spi/spi_ti_ssp.c        |    0 
>  drivers/spi/spi_tle62x0.c       |    0 
>  drivers/spi/spi_xilinx.c        |    0 
>  26 files changed, 192 insertions(+), 218 deletions(-)
>  delete mode 100644 drivers/spi/atmel_spi.h
>  rename drivers/spi/{ath79_spi.c => spi_ath79.c} (100%)
>  rename drivers/spi/{atmel_spi.c => spi_atmel.c} (85%)
>  rename drivers/spi/{au1550_spi.c => spi_au1550.c} (100%)
>  rename drivers/spi/{coldfire_qspi.c => spi_coldfire_qspi.c} (100%)
>  rename drivers/spi/{davinci_spi.c => spi_davinci.c} (100%)
>  rename drivers/spi/{dw_spi.c => spi_dw.c} (99%)
>  rename drivers/spi/{dw_spi.h => spi_dw.h} (100%)
>  rename drivers/spi/{dw_spi_mid.c => spi_dw_mid.c} (99%)
>  rename drivers/spi/{dw_spi_mmio.c => spi_dw_mmio.c} (99%)
>  rename drivers/spi/{dw_spi_pci.c => spi_dw_pci.c} (99%)
>  rename drivers/spi/{ep93xx_spi.c => spi_ep93xx.c} (100%)
>  rename drivers/spi/{mpc512x_psc_spi.c => spi_mpc512x_psc.c} (100%)
>  rename drivers/spi/{mpc52xx_spi.c => spi_mpc52xx.c} (100%)
>  rename drivers/spi/{mpc52xx_psc_spi.c => spi_mpc52xx_psc.c} (100%)
>  rename drivers/spi/{omap2_mcspi.c => spi_omap2_mcspi.c} (100%)
>  rename drivers/spi/{omap_spi_100k.c => spi_omap_100k.c} (100%)
>  rename drivers/spi/{omap_uwire.c => spi_omap_uwire.c} (100%)
>  rename drivers/spi/{orion_spi.c => spi_orion.c} (100%)
>  rename drivers/spi/{amba-pl022.c => spi_pl022.c} (100%)
>  rename drivers/spi/{pxa2xx_spi.c => spi_pxa2xx.c} (100%)
>  rename drivers/spi/{pxa2xx_spi_pci.c => spi_pxa2xx_pci.c} (100%)
>  rename drivers/spi/{ti-ssp-spi.c => spi_ti_ssp.c} (100%)
>  rename drivers/spi/{tle62x0.c => spi_tle62x0.c} (100%)
>  rename drivers/spi/{xilinx_spi.c => spi_xilinx.c} (100%)

We also have things like this in drivers/spi/Kconfig:

config SPI_DAVINCI
	...

	This driver can also be built as a module. The module will
	be called davinci_spi <--- This is now wrong

should these be converted as well?

  parent reply	other threads:[~2011-06-05  8:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-05  7:18 [PATCH] spi: reorganize drivers Grant Likely
2011-06-05  7:43 ` Jassi Brar
     [not found]   ` <BANLkTinoEQf2a65KwQZOVK_4H9DSfqybjA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-05  7:54     ` Baruch Siach
2011-06-05 11:49       ` Geert Uytterhoeven
2011-06-05 13:08         ` Stefan Richter
2011-06-05 20:55         ` Grant Likely
2011-06-05 21:19           ` Jassi Brar
2011-06-05 13:12       ` Jassi Brar
2011-06-05 20:57         ` Grant Likely
2011-06-05  8:13 ` Mika Westerberg [this message]
2011-06-05 14:37   ` Grant Likely
2011-06-06  9:00 ` Arnd Bergmann
2011-06-06  9:08   ` Dominik Brodowski
2011-06-06  9:08   ` Russell King - ARM Linux
2011-06-06  9:17   ` Jean Delvare
2011-06-06  9:29   ` James Bottomley
2011-06-06 11:21     ` Arnd Bergmann
2011-06-06 12:16       ` Jean Delvare
2011-06-06 12:35         ` Geert Uytterhoeven
     [not found]         ` <20110606141636.150c54b5-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-06-06 12:57           ` Arnd Bergmann
2011-06-06 13:44             ` Stefan Richter
2011-06-06 15:04               ` Arnd Bergmann
2011-06-06 10:01   ` Geert Uytterhoeven
2011-06-06 14:39   ` Grant Likely
2011-06-06 15:15     ` Russell King - ARM Linux

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=20110605081331.GA3499@acer \
    --to=mika.westerberg@iki.fi \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spi-devel-general@lists.sourceforge.net \
    /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).