From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/5] pinctrl: exynos: add exynos5410 SoC specific data
Date: Sun, 28 Dec 2014 20:16:24 +0900 [thread overview]
Message-ID: <549FE688.1060601@gmail.com> (raw)
In-Reply-To: <1416695185-5198-1-git-send-email-afaerber@suse.de>
Hi Andreas,
On 23.11.2014 07:26, Andreas F?rber 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
Any news on this patch? I'd like to ACK it, but apparently it is waiting
for a rebase.
Sorry for the delay, unfortunately things are a little bit busy on my
side nowadays.
Best regards,
Tomasz
next prev parent reply other threads:[~2014-12-28 11:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-22 20:26 [PATCH v2 0/5] ARM: EXYNOS: ODROID-XU DT and LEDs Andreas Färber
2014-11-22 20:26 ` [PATCH v2 1/5] ARM: dts: exynos5410: Clean up SMDK5410 indentation Andreas Färber
2014-11-22 20:26 ` [PATCH v2 2/5] ARM: dts: exynos5410: Prepare ODROID-XU device tree Andreas Färber
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
2014-11-30 12:13 ` Tomasz Figa
2014-12-28 11:16 ` Tomasz Figa [this message]
2014-11-22 20:26 ` [PATCH v2 4/5] ARM: dts: add pinctrl support to Exynos5410 Andreas Färber
2014-11-23 17:18 ` Andreas Färber
2014-11-23 17:20 ` [PATCH v3 " Andreas Färber
2014-11-22 20:26 ` [PATCH v2 5/5] ARM: dts: exynos5410: Add ODROID-XU LEDs Andreas Färber
2014-11-23 1:31 ` Andreas Färber
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=549FE688.1060601@gmail.com \
--to=tomasz.figa@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).