From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
Grant Likely <grant@secretlab.ca>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] h8300: Move gpio.h to gpio-internal.h
Date: Tue, 25 Oct 2011 00:32:24 +0200 [thread overview]
Message-ID: <20111024223223.GA4351@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20111024221004.GE4394@ponder.secretlab.ca>
On Tue, Oct 25, 2011 at 12:10:04AM +0200, Grant Likely wrote:
> This of course should go via the h8300 tree instead of the gpio tree.
If you look at the commit history there's not been much h8300 specific
work going on for quite some time now - all the commits have been going
via other trees - so since it's basically a gpiolib cleanup I figure
it'd be less work for Sato-san if you were able to pick it up.
next prev parent reply other threads:[~2011-10-24 22:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 21:59 [PATCH] h8300: Move gpio.h to gpio-internal.h Mark Brown
2011-10-24 22:10 ` Grant Likely
2011-10-24 22:32 ` Mark Brown [this message]
2011-10-24 22:40 ` Grant Likely
2011-10-25 5:55 ` Yoshinori Sato
2011-10-25 7:08 ` Mark Brown
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=20111024223223.GA4351@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=grant.likely@secretlab.ca \
--cc=grant@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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).