From: Grant Likely <grant.likely@secretlab.ca>
To: Mike Frysinger <vapier.adi@gmail.com>,
Dirk Brandewie <dirk.brandewie@gmail.com>
Cc: spi-devel-general@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] spi: reorganize drivers
Date: Mon, 6 Jun 2011 10:38:44 -0600 [thread overview]
Message-ID: <BANLkTinmfufSkSnmiKWWEgpaR-usbiV5tA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinqVf+uK+5T_X-EkXw-YE67DJL1Pg@mail.gmail.com>
On Mon, Jun 6, 2011 at 10:31 AM, Mike Frysinger <vapier.adi@gmail.com> wrote:
> On Mon, Jun 6, 2011 at 03:18, Grant Likely wrote:
>> Sort the SPI makefile and enforce the naming convention spi_*.c for
>> spi drivers.
>
> spi_topcliff_pch.c uses KBUILD_MODNAME with a few funcs, but perhaps
> those are only for /proc/ status tracking ? worth double checking ...
I just talked with Dirk Brandewie, who has a major rewrite to the
topcliff spi driver. I'll let him comment on whether or not changing
KBUILD_MODNAME will cause any problems.
g.
next prev parent reply other threads:[~2011-06-06 16:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 7:18 [PATCH v2] spi: reorganize drivers Grant Likely
2011-06-06 7:27 ` Wolfram Sang
2011-06-06 16:31 ` Mike Frysinger
2011-06-06 16:38 ` Grant Likely [this message]
2011-06-06 16:49 ` Dirk Brandewie
2011-06-06 16:52 ` Grant Likely
2011-06-07 4:32 ` Tomoya MORINAGA
2011-06-07 4:36 ` Mike Frysinger
2011-06-07 2:28 ` Feng Tang
2011-06-07 4:09 ` Grant Likely
[not found] ` <BANLkTim927Ld28JmVfALscThef02XQJDWw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-07 4:48 ` Feng Tang
2011-06-07 4:48 ` Mike Frysinger
2011-06-07 4:52 ` Du, Alek
2011-06-07 17:01 ` 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=BANLkTinmfufSkSnmiKWWEgpaR-usbiV5tA@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=dirk.brandewie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=vapier.adi@gmail.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;
as well as URLs for NNTP newsgroup(s).