From: Simon Horman <horms@verge.net.au>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Magnus Damm <magnus.damm@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
Wolfram Sang <wsa@the-dreams.de>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH 03/03] pinctrl: sh-pfc: r7s72100 SCIF2 port4, 6 and 8 support
Date: Tue, 3 Dec 2013 21:18:27 +0900 [thread overview]
Message-ID: <20131203121827.GE21976@verge.net.au> (raw)
In-Reply-To: <CACRpkdZMLe-uGPY0psjC_6+kdJecAvnjddnJTMkMNzg43DooiA@mail.gmail.com>
On Tue, Dec 03, 2013 at 10:36:54AM +0100, Linus Walleij wrote:
> On Wed, Nov 27, 2013 at 9:06 AM, Magnus Damm <magnus.damm@gmail.com> wrote:
>
> > From: Magnus Damm <damm@opensource.se>
> >
> > Add the remaining SCIF2 pins using the recently introduced macro.
> >
> > Signed-off-by: Magnus Damm <damm@opensource.se>
>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
>
> Laurent, please pick this into your stack for my tree.
>
> I guess the pure DTS changes can go directly to Simon's tree?
Yes, I'll pick them up.
next prev parent reply other threads:[~2013-12-03 12:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 8:06 [PATCH 00/03] pinctrl: sh-pfc: r7s72100 SCIF2 support Magnus Damm
2013-11-27 8:06 ` [PATCH 01/03] pinctrl: sh-pfc: r7s72100 SCIF2 port3 support Magnus Damm
2013-11-27 10:56 ` Laurent Pinchart
2013-11-29 10:29 ` Linus Walleij
2013-11-29 13:53 ` Laurent Pinchart
2013-11-27 8:06 ` [PATCH 02/03] pinctrl: sh-pfc: r7s72100 SCIF2 macro conversion Magnus Damm
2013-11-27 11:02 ` Laurent Pinchart
2013-11-27 8:06 ` [PATCH 03/03] pinctrl: sh-pfc: r7s72100 SCIF2 port4, 6 and 8 support Magnus Damm
2013-12-03 9:36 ` Linus Walleij
2013-12-03 12:18 ` Simon Horman [this message]
2013-12-04 1:09 ` 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=20131203121827.GE21976@verge.net.au \
--to=horms@verge.net.au \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=wsa@the-dreams.de \
/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
all inboxes | Powered by JetHome®