From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Simon Horman <horms@verge.net.au>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: [PATCH v2 00/27] sh-pfc: Support pins with no associated GPIO port
Date: Sat, 21 Sep 2013 20:56:07 +0200 [thread overview]
Message-ID: <1635782.W0dvDAedis@avalon> (raw)
In-Reply-To: <CACRpkdYFWJbHkwffrFes4o4btCGaZdXJxmxgxxMb_Mpc__5eQA@mail.gmail.com>
Hi Linus and Simon,
On Saturday 21 September 2013 10:59:20 Linus Walleij wrote:
> On Sat, Sep 21, 2013 at 2:43 AM, Simon Horman <horms@verge.net.au> wrote:
> > Hi Laurent,
> >
> > I am currently rebasing the renesas tree on v3.12-rc1 in preparation
> > for preparing pull-requests for v3.13. Should I continue to carry
> > sh-pfc/pins-with-no-gpio-port in devel?
>
> Sounds like something I should carry in the pinctrl tree?
The series has been merged in v3.12-rc1, no action is thus needed.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-09-21 18:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1373933479-17727-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
[not found] ` <11379562.iEdjek24uT@avalon>
[not found] ` <20130719021045.GE4403@verge.net.au>
2013-09-21 0:43 ` [PATCH v2 00/27] sh-pfc: Support pins with no associated GPIO port Simon Horman
2013-09-21 8:59 ` Linus Walleij
2013-09-21 18:56 ` Laurent Pinchart [this message]
2013-09-22 12:19 ` 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=1635782.W0dvDAedis@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).