From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] sh-pfc: r8a7791 PFC support
Date: Wed, 16 Oct 2013 15:16:27 +0900 [thread overview]
Message-ID: <20131016061626.GG15425@verge.net.au> (raw)
In-Reply-To: <17712286.HDNRip2xPu@avalon>
On Thu, Oct 10, 2013 at 12:43:17AM +0200, Laurent Pinchart wrote:
> Hi Magnus,
>
> On Tuesday 08 October 2013 13:08:24 Magnus Damm wrote:
> > From: Hisashi Nakamura <hisashi.nakamura.ak@renesas.com>
> >
> > Add PFC support for the r8a7791 SoC including pin groups for
> > on-chip devices such as MSIOF, SCIF, USB, MMC, VIN, SDHI, DU.
> >
> > Signed-off-by: Hisashi Nakamura <hisashi.nakamura.ak@renesas.com>
> > Signed-off-by: Kunihito Higashiyama <kunihito.higashiyama.ur@renesas.com>
> > Signed-off-by: Yoshikazu Fujikawa <yoshikazu.fujikawa.ue@renesas.com>
> > Signed-off-by: Nobuyuki HIRAI <nobuyuki.hirai.xe@renesas.com>
> > Signed-off-by: Shinobu Uehara <shinobu.uehara.xc@renesas.com>
> > Signed-off-by: Koji Matsuoka <koji.matsuoka.xm@renesas.com>
> > Signed-off-by: Ryo Kataoka <ryo.kataoka.wt@renesas.com>
> > [damm at opensource.se: Forward ported to upstream, reused existing sh-pfc
> > macros] Signed-off-by: Magnus Damm <damm@opensource.se>
>
> BTW, the patch was too big and didn't make it to the list :-/
I got it it anyway but if it doesn't hit the list it won't show
up in patchwork. And that is a minor problem for my work-flow
Magnus, when you repost this please ping me about it to
make sure it is on my radar.
prev parent reply other threads:[~2013-10-16 6:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131008040824.3480.69707.sendpatchset@w520>
2013-10-09 9:18 ` [PATCH] sh-pfc: r8a7791 PFC support Linus Walleij
2013-10-09 22:41 ` Laurent Pinchart
2013-10-15 3:42 ` Magnus Damm
2013-10-15 11:02 ` Laurent Pinchart
2013-10-09 22:43 ` Laurent Pinchart
2013-10-16 6:16 ` Simon Horman [this message]
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=20131016061626.GG15425@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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