From: "Andreas Färber" <afaerber@suse.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Tomasz Figa" <tomasz.figa@gmail.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
"Kukjin Kim" <kgene@kernel.org>, 김학주 <ruppi.kim@hardkernel.com>,
"Humberto Naves" <hsnaves@gmail.com>,
"Jan Kiszka" <jan.kiszka@siemens.com>,
"Johann Pfefferl" <johann.pfefferl@siemens.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Pawel Moll" <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Kumar Gala" <galak@codeaurora.org>,
"Thomas Abraham" <thomas.abraham@linaro.org>,
"Kukjin Kim" <kgene.kim@samsung.com>,
"OPEN FIRMWARE AND..." <devicetree@vger.kernel.org>,
"PIN CONTROL SUBSY..." <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v3 3/5] pinctrl: exynos: add exynos5410 SoC specific data
Date: Fri, 28 Nov 2014 13:07:03 +0100 [thread overview]
Message-ID: <54786567.4050305@suse.de> (raw)
In-Reply-To: <CACRpkdZie8JJGxSPkc8PPvC3qZkWhe5WqmpSKSoDFwqRd6tR_Q@mail.gmail.com>
Am 28.11.2014 um 12:59 schrieb Linus Walleij:
> On Sat, Nov 22, 2014 at 11:26 PM, Andreas Färber <afaerber@suse.de> wrote:
>
>> From: Hakjoo Kim <ruppi.kim@hardkernel.com>
>>
>> Add Samsung EXYNOS5410 SoC specific data to enable pinctrl
>> support for all platforms based on EXYNOS5410.
>>
>> Signed-off-by: Hakjoo Kim <ruppi.kim@hardkernel.com>
>> [AF: Rebased onto Exynos5260 and irq_chip consolidation]
>> Signed-off-by: Andreas Färber <afaerber@suse.de>
>> ---
>> v2 -> v3:
>> * Rebased (.svc, .{g,w}eint_{con,mask,pend} fields dropped)
>>
>> v1 -> v2:
>> * Filled in Sob from Hakjoo Kim
>
> Is this based on the pinctrl devel branch so I can apply it?
It was based on the Samsung for-next tree. I can rebase if needed.
> I'd like Tomasz ACK on it first though.
Thanks,
Andreas
--
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 21284 AG Nürnberg
next prev parent reply other threads:[~2014-11-28 12:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1416687984-3546-1-git-send-email-afaerber@suse.de>
2014-11-22 20:26 ` [PATCH v2 3/5] pinctrl: exynos: add exynos5410 SoC specific data Andreas Färber
2014-11-22 21:49 ` Andreas Färber
2014-11-22 22:26 ` [PATCH v3 " Andreas Färber
2014-11-28 11:59 ` Linus Walleij
2014-11-28 12:07 ` Andreas Färber [this message]
2014-11-30 12:13 ` Tomasz Figa
2014-12-28 11:16 ` Tomasz Figa
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=54786567.4050305@suse.de \
--to=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=hsnaves@gmail.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jan.kiszka@siemens.com \
--cc=johann.pfefferl@siemens.com \
--cc=kgene.kim@samsung.com \
--cc=kgene@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=ruppi.kim@hardkernel.com \
--cc=thomas.abraham@linaro.org \
--cc=tomasz.figa@gmail.com \
/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).