From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 00/02] sh-pfc: Initial r8a73a4 PFC support
Date: Tue, 19 Mar 2013 00:26:53 +0000 [thread overview]
Message-ID: <20130319002651.GA15718@verge.net.au> (raw)
In-Reply-To: <20130318145029.26761.15477.sendpatchset@w520>
On Mon, Mar 18, 2013 at 11:50:29PM +0900, Magnus Damm wrote:
> sh-pfc: Initial r8a73a4 PFC support
>
> [PATCH 01/02] sh-pfc: Add r8a73a4 pinmux support
> [PATCH 02/02] sh-pfc: Add r8a73a4 GPIO IRQ support
>
> This series is V1 of initial PFC support for the r8a73a4 SoC.
> Nothing out of the ordinary, just similar but different tables
> to describe the pinmux hardware and GPIOs on r8a73a4.
>
> The header in the mach directory is still used, and in the future
> this will be removed when fully using PINCTRL. Until then a common
> location is needed so this series simply follows what other SoCs
> do. Because of this there is a dependency on the r8a73a4 SoC code.
Laurent, could you review these and either give me some Acks or
a branch to pull? I assume the base should be the renesas-pinmux-for-v3.10 tag
in the renesas tree.
Thanks.
next prev parent reply other threads:[~2013-03-19 0:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 14:50 [PATCH 00/02] sh-pfc: Initial r8a73a4 PFC support Magnus Damm
2013-03-19 0:26 ` Simon Horman [this message]
2013-03-19 9:06 ` Simon Horman
2013-03-19 12: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=20130319002651.GA15718@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