public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: viresh kumar <viresh.kumar@linaro.org>, linux-kernel@vger.kernel.org
Cc: Paul Mundt <lethal@linux-sh.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	Simon Horman <horms@verge.net.au>,
	Linus Walleij <linus.walleij@linaro.org>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Phil Edworthy <phil.edworthy@renesas.com>,
	Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>,
	linux-sh@vger.kernel.org
Subject: Re: [PATCH 17/42] sh-pfc: Move driver from drivers/sh/ to drivers/pinctrl/
Date: Wed, 21 Nov 2012 13:17:29 +0000	[thread overview]
Message-ID: <1694290.k6RRrcIRbt@avalon> (raw)
In-Reply-To: <CAOh2x=kEv1Sgx74jNgdQJL4ivrYVpYhC0kM6--BTk+ibwRm3kg@mail.gmail.com>

Hi Viresh,

On Wednesday 21 November 2012 08:58:19 viresh kumar wrote:
> On Wed, Nov 21, 2012 at 7:57 AM, Laurent Pinchart wrote:
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>
> > ---
> > 
> >  drivers/pinctrl/Kconfig          |    1 +
> >  drivers/pinctrl/Makefile         |    1 +
> >  drivers/pinctrl/sh-pfc/Kconfig   |   24 ++
> >  drivers/pinctrl/sh-pfc/Makefile  |    5 +
> >  drivers/pinctrl/sh-pfc/core.c    |  611 +++++++++++++++++++++++++++++++++
> >  drivers/pinctrl/sh-pfc/core.h    |   54 ++++
> >  drivers/pinctrl/sh-pfc/gpio.c    |  181 +++++++++++
> >  drivers/pinctrl/sh-pfc/pinctrl.c |  481 ++++++++++++++++++++++++++++++
> >  drivers/sh/Kconfig               |    1 -
> >  drivers/sh/Makefile              |    1 -
> >  drivers/sh/pfc/Kconfig           |   18 --
> >  drivers/sh/pfc/Makefile          |    5 -
> >  drivers/sh/pfc/core.c            |  611 ---------------------------------
> >  drivers/sh/pfc/core.h            |   54 ----
> >  drivers/sh/pfc/gpio.c            |  181 -----------
> >  drivers/sh/pfc/pinctrl.c         |  481 ------------------------------
> 
> I haven't gone through the patch, but is it a simple git mv of files?
> If yes, please generate such patches with following command to make review
> really simple:
> 
> git format-patch -C -M

My bad. Will do in the next version.

-- 
Regards,

Laurent Pinchart


       reply	other threads:[~2012-11-21 13:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1353464863-10281-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
     [not found] ` <1353464863-10281-18-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
     [not found]   ` <CAOh2x=kEv1Sgx74jNgdQJL4ivrYVpYhC0kM6--BTk+ibwRm3kg@mail.gmail.com>
2012-11-21 13:17     ` Laurent Pinchart [this message]
     [not found] ` <1353464863-10281-24-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
     [not found]   ` <CABMQnVJU5nfgLzYX9HavNuCxxD5Ei10hbed2Uz1wth-nDse-+Q@mail.gmail.com>
2012-11-22 11:12     ` [PATCH 23/42] sh-pfc: Add sh7377 pinmux support Laurent Pinchart
2012-11-21  2:53 [PATCH 17/42] sh-pfc: Move driver from drivers/sh/ to drivers/pinctrl/ 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=1694290.k6RRrcIRbt@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=horms@verge.net.au \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lethal@linux-sh.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=nobuhiro.iwamatsu.yj@renesas.com \
    --cc=phil.edworthy@renesas.com \
    --cc=viresh.kumar@linaro.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