From: Linus Walleij <linus.walleij@linaro.org>
To: "Niklas Söderlund" <niso@kth.se>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH v3] sh-pfc: Add emev2 pinmux support
Date: Tue, 27 Jan 2015 08:52:18 +0100 [thread overview]
Message-ID: <CACRpkdZ4pCTz7kU6mCGqPUUtOr66NP84gkaQB++Ojkh-61PHWA@mail.gmail.com> (raw)
In-Reply-To: <1422193792-15970-1-git-send-email-niso@kth.se>
On Sun, Jan 25, 2015 at 2:49 PM, Niklas Söderlund <niso@kth.se> wrote:
> Add PFC support for the EMMA Mobile EV2 SoC including pin groups for
> on-chip devices.
>
> Signed-off-by: Niklas Söderlund <niso@kth.se>
This v3 version applied with Laurent's ACK.
Yours,
Linus Walleij
next prev parent reply other threads:[~2015-01-27 7:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 12:20 [PATCH v2 0/4] Add emev2 pinmux support Niklas Söderlund
[not found] ` <1421583604-27256-1-git-send-email-niso-UNjuZkX4dYU@public.gmane.org>
2015-01-18 12:20 ` [PATCH v2 1/4] sh-pfc: add macro to define pinmux without function Niklas Söderlund
[not found] ` <1421583604-27256-2-git-send-email-niso-UNjuZkX4dYU@public.gmane.org>
2015-01-22 21:50 ` Laurent Pinchart
2015-01-27 7:48 ` Linus Walleij
2015-01-18 12:20 ` [PATCH v2 4/4] ARM: shmobile: emev2-kzm9d: Add PFC information for uart1 Niklas Söderlund
2015-01-27 7:55 ` Linus Walleij
2015-01-27 20:31 ` [RFC/PATCH] pinctrl: sh-pfc: Accept standard function, pins and groups properties Laurent Pinchart
2015-01-27 20:40 ` Geert Uytterhoeven
2015-02-04 8:40 ` Linus Walleij
[not found] ` <CACRpkda6H7hbgXhmSbgtwOC_8PbHnES5syp-YEp1+V6s5Ym6Cw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-04 9:53 ` Laurent Pinchart
2015-03-01 12:19 ` Laurent Pinchart
2015-03-06 10:39 ` Linus Walleij
[not found] ` <CACRpkdbepTKxMFVpTo7ZmjYE1beF5XOMOQarszaDGojerNQqMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-09 14:35 ` Geert Uytterhoeven
[not found] ` <CAMuHMdWp4iBGtR2EiYMa03hwJrSOpq9dB==yDgt+OwjCebuFMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-10 8:46 ` Linus Walleij
2015-01-27 20:35 ` [PATCH v2 4/4] ARM: shmobile: emev2-kzm9d: Add PFC information for uart1 Laurent Pinchart
2015-01-18 12:20 ` [PATCH v2 2/4] sh-pfc: Add emev2 pinmux support Niklas Söderlund
2015-01-22 22:37 ` Laurent Pinchart
2015-01-25 13:48 ` Niklas Söderlund
[not found] ` <20150125134823.GA26657-ofJ5d6taAgLV0csKaCxRng@public.gmane.org>
2015-01-25 15:55 ` Laurent Pinchart
2015-01-25 13:49 ` [PATCH v3] " Niklas Söderlund
2015-01-25 16:05 ` Laurent Pinchart
2015-01-27 7:52 ` Linus Walleij [this message]
2015-01-18 12:20 ` [PATCH v2 3/4] ARM: shmobile: emev2: Add PFC information to emev2.dtsi Niklas Söderlund
2015-01-22 21:50 ` Laurent Pinchart
2015-01-27 7:53 ` Linus Walleij
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=CACRpkdZ4pCTz7kU6mCGqPUUtOr66NP84gkaQB++Ojkh-61PHWA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=niso@kth.se \
/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).