From: Linus Walleij <linus.walleij@linaro.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH 0/4] pinctrl: sh-pfc: More PINMUX_SINGLE() conversions
Date: Tue, 16 Feb 2016 16:19:20 +0100 [thread overview]
Message-ID: <CACRpkdbTjeOb_BpdMm5uVLGDSj_w=1r0de1mYLCDgc0Di22zVg@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdWuMLd+xah5H8a7XY2WY1QcCus+x+jcju2p9Mw4Q1yGVg@mail.gmail.com>
On Mon, Feb 15, 2016 at 7:39 PM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> On Mon, Feb 15, 2016 at 7:26 PM, Linus Walleij <linus.walleij@linaro.org> wrote:
>> On Mon, Nov 30, 2015 at 2:41 PM, Geert Uytterhoeven
>> <geert+renesas@glider.be> wrote:
>>> This patch series converts pin control data for a few more Renesas SoCs
>>> to the recently-introduced PINMUX_SINGLE() macro.
>>> As such this series depends on "[PATCH/RFC 0/4] pinctrl: sh-pfc: Add
>>> PINMUX_SINGLE()".
>>
>> Looks good to me (TM)
>> Please queue them and send with a pull request incl. Laurent's ACKs.
>
> Been there, done that. This series is already in v4.5-rc1 ;-)
Hehe you know I get too much mail when I get this kind of Alzheimer
behaviour...
Thanks.
Yours,
Linus Walleij
prev parent reply other threads:[~2016-02-16 15:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 13:41 [PATCH 0/4] pinctrl: sh-pfc: More PINMUX_SINGLE() conversions Geert Uytterhoeven
2015-11-30 13:41 ` [PATCH 1/4] pinctrl: sh-pfc: emev2: Use PINMUX_SINGLE() instead of raw PINMUX_DATA() Geert Uytterhoeven
2015-11-30 13:41 ` [PATCH 2/4] pinctrl: sh-pfc: r8a7778: " Geert Uytterhoeven
2015-11-30 13:41 ` [PATCH 3/4] pinctrl: sh-pfc: r8a7779: " Geert Uytterhoeven
2015-11-30 13:41 ` [PATCH 4/4] pinctrl: sh-pfc: sh7734: " Geert Uytterhoeven
2016-02-04 18:51 ` [PATCH 0/4] pinctrl: sh-pfc: More PINMUX_SINGLE() conversions Laurent Pinchart
2016-02-15 18:26 ` Linus Walleij
2016-02-15 18:39 ` Geert Uytterhoeven
2016-02-16 15:19 ` Linus Walleij [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='CACRpkdbTjeOb_BpdMm5uVLGDSj_w=1r0de1mYLCDgc0Di22zVg@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-gpio@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).