linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/4 v2] ARM: shmobile: r8a7778: pinctrl support
Date: Thu, 11 Apr 2013 00:45:24 +0000	[thread overview]
Message-ID: <20130411004524.GF1205@verge.net.au> (raw)
In-Reply-To: <87hajeka2q.wl%kuninori.morimoto.gx@renesas.com>

On Wed, Apr 10, 2013 at 12:58:47PM +0200, Laurent Pinchart wrote:
> Hi Morimoto-san,
> 
> On Wednesday 10 April 2013 02:29:37 Kuninori Morimoto wrote:
> > Hi Laurent, Simon, Magnus
> > 
> > These patches are v2 of r8a7778 pinctrl support
> > I removed [RFC] from Subject
> > 
> > These are based on
> > 
> > renesas-next-20130405v2
> >  + simon/defconfig-bockw
> >  + simon/soc-r8a7778
> >  + simon/boards-bockw
> > 
> > and Laurent's this patch
> > 
> > Subject: [PATCH v2 1/3] gpio-rcar: Add RCAR_GP_PIN macro
> > Date:	Mon,  8 Apr 2013 12:05:30 +0200
> > 
> > Kuninori Morimoto (3):
> >       sh-pfc: Add r8a7778 pinmux support
> >       ARM: shmobile: r8a7778: Register PFC device
> >       ARM: shmobile: bockw: add pinctrl support
> 
> The patches look good, I just had a couple of comments on 1/3. I've acked 2/3 
> and 3/3 already from v1, could you pick up the acks and add them to v3 ? In 
> general picking Acked-by, Reviewed-by and Tested-by lines from the list when 
> submitting a new version is a good idea, as it helps reviewer skip patches 
> they have already reviewed.

It also helps the maintainer not to forget to add them :^)

  parent reply	other threads:[~2013-04-11  0:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10  9:29 [PATCH 0/4 v2] ARM: shmobile: r8a7778: pinctrl support Kuninori Morimoto
2013-04-10 10:58 ` Laurent Pinchart
2013-04-11  0:45 ` Simon Horman [this message]
2013-04-11  2:49 ` Kuninori Morimoto
2013-04-15 10:35 ` 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=20130411004524.GF1205@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).