From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 0/8] Use gpio_request_one() in SH Mobile board code
Date: Mon, 28 Jan 2013 01:01:38 +0000 [thread overview]
Message-ID: <20130128010137.GH3423@verge.net.au> (raw)
In-Reply-To: <1359029795-7871-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
On Mon, Jan 28, 2013 at 09:50:58AM +0900, Simon Horman wrote:
> On Fri, Jan 25, 2013 at 11:13:13AM +0100, Guennadi Liakhovetski wrote:
> > Hi Laurent
> >
> > On Thu, 24 Jan 2013, Laurent Pinchart wrote:
> >
> > > Hello,
> > >
> > > Here are the second version of the gpio_request_one() patches for all SH Mobile
> > > board files.
> > >
> > > Compared to v1 the patches have been rebased on top of "[PATCH v4 00/81] SH pin
> > > control and GPIO rework", as the previous base isn't ready for mainline yet.
> > > The patches are otherwise unchanged.
> > >
> > > Simon, with the appropriate acks I think this series could go to v3.9. If you
> > > would like a pull request, on which of your branches should I rebase the
> > > patches ? I've tried to rebase them on top of your current next branch and they
> > > apply fine, so picking them up from the mailing list shouldn't be an issue
> > > either.
> > >
> > > Laurent Pinchart (8):
> >
> > All look good to me:
> >
> > Acked-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
>
> Thanks, I'll apply this series.
I have applied them to the boards2 branch, which I plan to send a
pull-request for once the pull-request boards branch, which boards2 is
based on, has been accepted (or rejected!).
I have also merged the changes into the next branch so they should
appear in linux-next in the not too distant future.
prev parent reply other threads:[~2013-01-28 1:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 12:16 [PATCH v2 0/8] Use gpio_request_one() in SH Mobile board code Laurent Pinchart
2013-01-25 2:31 ` Simon Horman
2013-01-25 9:55 ` Laurent Pinchart
2013-01-25 10:13 ` Guennadi Liakhovetski
2013-01-28 0:50 ` Simon Horman
2013-01-28 1:01 ` Simon Horman [this message]
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=20130128010137.GH3423@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;
as well as URLs for NNTP newsgroup(s).