From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
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>,
Simon Horman <horms@verge.net.au>
Subject: Re: [PATCH 01/03] pinctrl: sh-pfc: r7s72100 SCIF2 port3 support
Date: Fri, 29 Nov 2013 13:53:43 +0000 [thread overview]
Message-ID: <1644283.pjijxmSWPQ@avalon> (raw)
In-Reply-To: <CACRpkdbUvitwMQ+YjMonCZAJR_9VZMai_4etZE091vDHdFWZmA@mail.gmail.com>
Hi Linus,
On Friday 29 November 2013 11:29:51 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 support for SCIF2 port3 pin functions SCK, TXD and RXD to the
> > r7s72100 PINCTRL code. There are two possible pins that can be used
> > for TXD (Port 3 Pin 0 Function 6 and Port 3 Pin 1 Function 4) and
> > because of that are the data pins broken out in separate TXD and RXD.
> >
> > This format is similar to other sh-pfc code, but a following patch
> > converts this to less verbose and less readable code.
> >
> > Signed-off-by: Magnus Damm <damm@opensource.se>
>
> Regarding this and other PFC patches: Laurent can you help me
> out with collecting the patches for my pinctrl tree and send me
> a pull request when it's all tested together, like you did in the
> last kernel cycle?
Sure, will do.
--
Regards,
Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
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>,
Simon Horman <horms@verge.net.au>
Subject: Re: [PATCH 01/03] pinctrl: sh-pfc: r7s72100 SCIF2 port3 support
Date: Fri, 29 Nov 2013 14:53:43 +0100 [thread overview]
Message-ID: <1644283.pjijxmSWPQ@avalon> (raw)
In-Reply-To: <CACRpkdbUvitwMQ+YjMonCZAJR_9VZMai_4etZE091vDHdFWZmA@mail.gmail.com>
Hi Linus,
On Friday 29 November 2013 11:29:51 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 support for SCIF2 port3 pin functions SCK, TXD and RXD to the
> > r7s72100 PINCTRL code. There are two possible pins that can be used
> > for TXD (Port 3 Pin 0 Function 6 and Port 3 Pin 1 Function 4) and
> > because of that are the data pins broken out in separate TXD and RXD.
> >
> > This format is similar to other sh-pfc code, but a following patch
> > converts this to less verbose and less readable code.
> >
> > Signed-off-by: Magnus Damm <damm@opensource.se>
>
> Regarding this and other PFC patches: Laurent can you help me
> out with collecting the patches for my pinctrl tree and send me
> a pull request when it's all tested together, like you did in the
> last kernel cycle?
Sure, will do.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-11-29 13:53 UTC|newest]
Thread overview: 22+ 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 ` Magnus Damm
2013-11-27 8:06 ` [PATCH 01/03] pinctrl: sh-pfc: r7s72100 SCIF2 port3 support Magnus Damm
2013-11-27 8:06 ` Magnus Damm
2013-11-27 10:56 ` Laurent Pinchart
2013-11-27 10:56 ` Laurent Pinchart
2013-11-29 10:29 ` Linus Walleij
2013-11-29 10:29 ` Linus Walleij
2013-11-29 13:53 ` Laurent Pinchart [this message]
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 8:06 ` Magnus Damm
2013-11-27 11:02 ` Laurent Pinchart
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-11-27 8:06 ` Magnus Damm
2013-12-03 9:36 ` Linus Walleij
2013-12-03 9:36 ` Linus Walleij
2013-12-03 12:18 ` Simon Horman
2013-12-03 12:18 ` Simon Horman
2013-12-04 1:09 ` Laurent Pinchart
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=1644283.pjijxmSWPQ@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=horms@verge.net.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.