From: Mike Frysinger <vapier.adi@gmail.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpio: reorganize drivers
Date: Mon, 6 Jun 2011 12:29:49 -0400 [thread overview]
Message-ID: <BANLkTiko2A3bthjVL_NR0yaQP_8Nq5VmqQ@mail.gmail.com> (raw)
In-Reply-To: <20110606070553.9829.40823.stgit@ponder>
On Mon, Jun 6, 2011 at 03:06, Grant Likely wrote:
> Sort the gpio makefile and enforce the naming convention gpio-*.c for
> gpio drivers.
ml_ioh_gpio.c and pch_gpio.c use KBUILD_MODNAME with
pci_request_regions, but i think that func only uses it for /proc/
status info, so maybe it's ok ?
-mike
next prev parent reply other threads:[~2011-06-06 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 7:06 [PATCH] gpio: reorganize drivers Grant Likely
2011-06-06 16:29 ` Mike Frysinger [this message]
2011-06-06 16:43 ` Grant Likely
2011-06-07 4:34 ` Tomoya MORINAGA
2011-06-06 17:27 ` Roland Dreier
2011-06-06 17:33 ` Grant Likely
2011-06-06 17:37 ` Grant Likely
2011-06-07 4:39 ` Mike Frysinger
2011-06-08 16:56 ` Roland Dreier
-- strict thread matches above, loose matches on Subject: below --
2011-06-05 7:16 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=BANLkTiko2A3bthjVL_NR0yaQP_8Nq5VmqQ@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
/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).