From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
"Jean Delvare (PC drivers, core)" <khali@linux-fr.org>,
"Ben Dooks (embedded platforms)" <ben-linux@fluff.org>,
linux-pcmcia@lists.infradead.org,
Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>,
"David S. Miller" <davem@davemloft.net>,
Michael Buesch <mb@bu3sch.de>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Florian Fainelli <florian@openwrt.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
spi-devel-general@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Russell King <linux@arm.linux.org.uk>
Subject: Re: [PATCH] spi: reorganize drivers
Date: Mon, 06 Jun 2011 18:29:07 +0900 [thread overview]
Message-ID: <1307352547.7586.6.camel@mulgrave.site> (raw)
In-Reply-To: <201106061100.38249.arnd@arndb.de>
On Mon, 2011-06-06 at 11:00 +0200, Arnd Bergmann wrote:
> On Sunday 05 June 2011, Grant Likely wrote:
> > 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%)
>
> I recently looked at the directory structure in drivers/ and found a lot
> of bus drivers with very few files, plus a few bus drivers with a lot
> of files in them besides directories for non-bus specific subsystems.
>
> I think it would be good to move them into a deeper directory drivers/bus/
> if we have support from the maintainers, and it's probably better if we
> only have to move the files once to reduce the amount of churn on the
> MAINTAINERS file and any out of tree patches.
>
> Specifically, I'd like to do these moves:
>
> drivers/{ => bus}/amba
> drivers/{ => bus}/dio
> drivers/{ => bus}/eisa
> drivers/{ => bus}/firewire
> drivers/{ => bus}/i2c
> drivers/{ => bus}/mca
> drivers/{ => bus}/nubus
> drivers/{ => bus}/pcmcia
> drivers/{ => bus}/rapidio
> drivers/{ => bus}/sbus
> drivers/{ => bus}/spi
> drivers/{ => bus}/ssb
> drivers/{ => bus}/tc
> drivers/{ => bus}/uwb
> drivers/{ => bus}/virtio
> drivers/{ => bus}/vlync
> drivers/{ => bus}/w1
> drivers/{ => bus}/zorro
>
> This leaves out the two most common buses, USB and PCI, mostly because
> the directories contain a lot of stuff that is not really bus code
> but actual drivers. It does include i2c and spi, which stick out by
> being a lot larger than most others.
>
> Opinions? Move or don't move?
I'd say it only makes sense if we do it for all busses ... so USB and
PCI would have to move too. Logically, the bus code should move and we
should be left with the drivers in both of those directories. I'd also
say that we don't have to deepen the tree: /bus would be fine. That
way, /drivers/<bus> would be only for <bus> specific drivers, with non
bus specific drivers we just group them by function as now.
What about the half busses (like SCSI)?
Finally, is there any real point (other than we can do it)? what is
actually helped by having the bus code obviously separated from the
driver code (assuming we sort out what is bus and what is driver)?
James
next prev parent reply other threads:[~2011-06-06 9:29 UTC|newest]
Thread overview: 28+ 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
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
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 [this message]
2011-06-06 11:21 ` Arnd Bergmann
2011-06-06 12:16 ` Jean Delvare
2011-06-06 12:35 ` Geert Uytterhoeven
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
-- strict thread matches above, loose matches on Subject: below --
2011-06-05 7:13 Grant Likely
2011-06-07 9:28 ` Linus Walleij
2011-06-07 13:26 ` Grant Likely
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=1307352547.7586.6.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=alexandre.bounine@idt.com \
--cc=arnd@arndb.de \
--cc=ben-linux@fluff.org \
--cc=davem@davemloft.net \
--cc=florian@openwrt.org \
--cc=geert@linux-m68k.org \
--cc=grant.likely@secretlab.ca \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=macro@linux-mips.org \
--cc=mb@bu3sch.de \
--cc=mporter@kernel.crashing.org \
--cc=rusty@rustcorp.com.au \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.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).