From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 0/3] sh-pfc: r8a7779: Improve readability with a new macro
Date: Tue, 09 Apr 2013 13:14:40 +0000 [thread overview]
Message-ID: <1886899.CCYkyRRy3m@avalon> (raw)
In-Reply-To: <1365415532-24544-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
Hi Simon,
On Tuesday 09 April 2013 22:13:25 Simon Horman wrote:
> On 月, 4月 08, 2013 at 12:05:29午後 +0200, Laurent Pinchart wrote:
> > Hello,
> >
> > This is the second version of the r8a7779 PFC readability improvement
> > patches that use a macro to convert from the documentation pin number
> > space to the linear pinctrl space.
> >
> > Note that patch 1/3 has already been posted as part of the "r8a7790 PFC
> > pinctrl and GPIO improvements" patch series. Depending on the merge order
> > one of them should be dropped.
> >
> > Simon, is there a chance you could queue this to your pinmux branch for
> > v3.10 ?
>
> If it is urgent, yes. Otherwise I'd prefer to wait for v3.11.
That's fine with me.
> In any case, Magnus, can I get a review?
>
> > Changes from v1:
> >
> > - Rename the macro to RCAR_GP_PIN
> > - Define the macro in a single header file
> >
> > Laurent Pinchart (3):
> > gpio-rcar: Add RCAR_GP_PIN macro
> > sh-pfc: r8a7779: Replace hardcoded pin numbers with RCAR_GP_PIN macro
> > ARM: shmobile: marzen: Use RCAR_GP_PIN macro
> >
> > arch/arm/mach-shmobile/board-marzen.c | 7 +-
> > drivers/pinctrl/sh-pfc/pfc-r8a7779.c | 294 +++++++++++++++------------
> > include/linux/platform_data/gpio-rcar.h | 2 +
> > 3 files changed, 170 insertions(+), 133 deletions(-)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-04-09 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 10:05 [PATCH v2 0/3] sh-pfc: r8a7779: Improve readability with a new macro Laurent Pinchart
2013-04-09 13:13 ` Simon Horman
2013-04-09 13:14 ` Laurent Pinchart [this message]
2013-04-11 8:07 ` Simon Horman
2013-04-22 3:31 ` 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=1886899.CCYkyRRy3m@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox