From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH/RFC 2/3] pinctrl: sh-pfc: add pin groups for all SD/MMC interfaces on sh73a0
Date: Thu, 14 Feb 2013 00:39:28 +0000 [thread overview]
Message-ID: <20130214003928.GD15879@verge.net.au> (raw)
In-Reply-To: <1360684204-12888-3-git-send-email-g.liakhovetski@gmx.de>
On Wed, Feb 13, 2013 at 07:07:20PM +0100, Laurent Pinchart wrote:
> Hi Guennadi,
>
> Thanks for the patch.
>
> On Tuesday 12 February 2013 16:50:03 Guennadi Liakhovetski wrote:
> > Add pin group definitions for SDHI0, SDHI1, SDHI2 and MMCIF interfaces on
> > sh73a0.
> >
> > Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
>
> As this patch doesn't strictly depend on 1/3 I've taken it in my tree. I will
> push it along with a sparse GPIO numbering fix (I'm currently reviewing 1/3).
Thanks. To clarify that will go via Linus's tree?
next prev parent reply other threads:[~2013-02-14 0:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 15:50 [PATCH/RFC 2/3] pinctrl: sh-pfc: add pin groups for all SD/MMC interfaces on sh73a0 Guennadi Liakhovetski
2013-02-13 4:31 ` Simon Horman
2013-02-13 18:07 ` Laurent Pinchart
2013-02-14 0:39 ` Simon Horman [this message]
2013-02-14 11:11 ` Laurent Pinchart
2013-02-14 12:11 ` Linus Walleij
2013-02-14 15:58 ` Simon Horman
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=20130214003928.GD15879@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@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