From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 00/27] sh-pfc: Support pins with no associated GPIO port
Date: Wed, 24 Jul 2013 13:28:01 +0000 [thread overview]
Message-ID: <1882949.fNUBemKiGK@avalon> (raw)
In-Reply-To: <1373933479-17727-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
Hi Linus,
On Sunday 21 July 2013 00:19:36 Linus Walleij wrote:
> On Thu, Jul 18, 2013 at 3:24 AM, Laurent Pinchart wrote:
> > Hi Simon,
> >
> > I've received a positive test feedback for this patch series. Could you
> > please include it in your -devel tags to get wider test coverage ? I'll
> > then wait a couple of weeks and, if no problem is found, send a pull
> > request to Linus to get the series merged through the pinctrl tree.
>
> That's very helpful, I can then pull it in and inspect the files before and
> after this train of patches, which is probably the most efficient way to
> review it.
The patches can be found in my git tree at
git://linuxtv.org/pinchartl/fbdev.git pinmux/next/pin-no-gpio
If you have time, could you already review them ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-07-24 13:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 0:10 [PATCH v2 00/27] sh-pfc: Support pins with no associated GPIO port Laurent Pinchart
2013-07-18 1:24 ` Laurent Pinchart
2013-07-19 2:10 ` Simon Horman
2013-09-21 0:43 ` Simon Horman
2013-09-21 0:43 ` Simon Horman
2013-09-21 8:59 ` Linus Walleij
2013-09-21 8:59 ` Linus Walleij
2013-09-21 18:56 ` Laurent Pinchart
2013-09-21 18:56 ` Laurent Pinchart
2013-09-22 12:19 ` Simon Horman
2013-09-22 12:19 ` Simon Horman
2013-07-20 22:19 ` Linus Walleij
2013-07-24 13:28 ` Laurent Pinchart [this message]
2013-07-26 23:14 ` Linus Walleij
2013-07-29 13:22 ` Laurent Pinchart
2013-07-29 14:32 ` Linus Walleij
2013-07-29 14:34 ` Laurent Pinchart
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=1882949.fNUBemKiGK@avalon \
--to=laurent.pinchart@ideasonboard.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.