From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Baruch Siach <baruch@tkos.co.il>,
Grant Likely <grant.likely@secretlab.ca>,
Jassi Brar <jassisinghbrar@gmail.com>,
spi-devel-general@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: reorganize drivers
Date: Sun, 5 Jun 2011 15:08:07 +0200 [thread overview]
Message-ID: <20110605150807.0cb01ba0@stein> (raw)
In-Reply-To: <BANLkTi=5XLxcZiBcZT8W4Gh+Ph_BUjs-yw@mail.gmail.com>
On Jun 05 Geert Uytterhoeven wrote:
> On Sun, Jun 5, 2011 at 09:54, Baruch Siach <baruch@tkos.co.il> wrote:
> > On Sun, Jun 05, 2011 at 01:13:28PM +0530, Jassi Brar wrote:
> >> On Sun, Jun 5, 2011 at 12:48 PM, Grant Likely <grant.likely@secretlab.ca> 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.
> >
> > [snip]
> >
> >> Though the spi_ prefix seems redundant considering the files are in
> >> 'spi' directory.
> >> Just a thought, no objection.
> >
> > When looking at the list of loaded modules (e.g. in an Oops message), the name
> > "spi_xilinx" is much more meaningful than just "xilinx", for example.
>
> Plus, when dropping the prefix, spi_xilinx.ko and gpio-xilinx.ko
> become the same...
In drivers/firewire/Makefile for example, there is this:
firewire-core-y += core-card.o core-cdev.o core-device.o \
core-iso.o core-topology.o core-transaction.o
firewire-ohci-y += ohci.o
firewire-sbp2-y += sbp2.o
firewire-net-y += net.o
Which is impractical though if there are more than a handful of drivers
involved.
--
Stefan Richter
-=====-==-== -==- --=-=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2011-06-05 13:08 UTC|newest]
Thread overview: 40+ 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 7:54 ` Baruch Siach
2011-06-05 11:49 ` Geert Uytterhoeven
2011-06-05 13:08 ` Stefan Richter [this message]
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:00 ` Arnd Bergmann
2011-06-06 9:08 ` Dominik Brodowski
2011-06-06 9:08 ` Russell King - ARM Linux
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 11:21 ` Arnd Bergmann
2011-06-06 12:16 ` Jean Delvare
2011-06-06 12:16 ` Jean Delvare
2011-06-06 12:35 ` Geert Uytterhoeven
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 12:57 ` Arnd Bergmann
2011-06-06 13:44 ` Stefan Richter
2011-06-06 13:44 ` Stefan Richter
2011-06-06 15:04 ` Arnd Bergmann
2011-06-06 15:04 ` Arnd Bergmann
2011-06-06 10:01 ` Geert Uytterhoeven
2011-06-06 10:01 ` Geert Uytterhoeven
2011-06-06 14:39 ` Grant Likely
2011-06-06 14:39 ` Grant Likely
2011-06-06 15:15 ` Russell King - ARM Linux
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=20110605150807.0cb01ba0@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=baruch@tkos.co.il \
--cc=geert@linux-m68k.org \
--cc=grant.likely@secretlab.ca \
--cc=jassisinghbrar@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.