From: Ben Gamari <bgamari.foss@gmail.com>
To: "Andreas Färber" <afaerber@suse.de>,
linux-samsung-soc@vger.kernel.org,
"Kukjin Kim" <kgene.kim@samsung.com>
Cc: Humberto Naves <hsnaves@gmail.com>,
Tarek Dakhran <t.dakhran@samsung.com>,
Kevin Hilman <khilman@linaro.org>,
linux-kernel@vger.kernel.org,
Hakjoo Kim <ruppi.kim@hardkernel.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC 0/5] ARM: EXYNOS: ODROID-XU DT and LEDs
Date: Sat, 14 Mar 2015 15:13:29 -0400 [thread overview]
Message-ID: <87oanv9yue.fsf@gmail.com> (raw)
In-Reply-To: <53D9CA35.1030800@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]
Andreas Färber <afaerber@suse.de> writes:
> Kukjin,
>
> Am 28.07.2014 14:18, schrieb Andreas Färber:
>> Hello,
>>
>> This series adds a dedicated ODROID-XU device tree and enhances it with
>> LED configuration, to match the downstream 3.14 based behavior.
>>
>> It had turned out less trivial than I initially thought as the whole
>> pinctrl stuff is still missing. I thus cherry-pick two downstream commits.
>>
>> Hakjoo, can you please reply with a Signed-off-by to your patches
>> so that we can get them into upstream? Thanks in advance!
>
> FTR, Hakjoo Kim did reply with signed off patches (thanks again!) and
> updated their branch accordingly:
>
> https://github.com/hardkernel/linux/commits/odroid-3.14.y-linaro
> https://github.com/hardkernel/linux/commit/53edc3da0d1da287517681b47daf36679637b6ba
> https://github.com/hardkernel/linux/commit/afdc310e47e4d1799719566bfb5a47c55141a7cb
>
>> Andreas Färber (3):
>> ARM: dts: exynos5410: Clean up SMDK5410 indentation
>> ARM: dts: exynos5410: Prepare ODROID-XU device tree
>
> The functional changes below haven't been reviewed yet, but could you
> consider applying trivial patches 1-2?
>
> Regards,
> Andreas
>
>> ARM: dts: exynos5410: Add ODROID-XU LEDs
>>
>> Hakjoo Kim (2):
>> pinctrl: exynos: add exynos5410 SoC specific data
>> ARM: dts: add pinctrl support to Exynos5410
>>
What happened with this set? It appears that 1-2 were never merged nor
was there any review of the remaining patches.
Cheers,
- Ben
[-- Attachment #2: Type: application/pgp-signature, Size: 472 bytes --]
prev parent reply other threads:[~2015-03-14 19:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 12:18 [RFC 0/5] ARM: EXYNOS: ODROID-XU DT and LEDs Andreas Färber
2014-07-28 12:18 ` [PATCH 1/5] ARM: dts: exynos5410: Clean up SMDK5410 indentation Andreas Färber
2014-07-28 12:18 ` [PATCH 2/5] ARM: dts: exynos5410: Prepare ODROID-XU device tree Andreas Färber
2014-07-28 12:18 ` [RFC 3/5] pinctrl: exynos: add exynos5410 SoC specific data Andreas Färber
2014-08-08 12:55 ` Linus Walleij
2014-08-08 13:20 ` Tomasz Figa
2014-07-28 12:18 ` [RFC 4/5] ARM: dts: add pinctrl support to Exynos5410 Andreas Färber
2014-08-08 13:29 ` Tomasz Figa
2014-07-28 12:18 ` [RFC 5/5] ARM: dts: exynos5410: Add ODROID-XU LEDs Andreas Färber
2014-07-31 4:46 ` [RFC 0/5] ARM: EXYNOS: ODROID-XU DT and LEDs Andreas Färber
2015-03-14 19:13 ` Ben Gamari [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=87oanv9yue.fsf@gmail.com \
--to=bgamari.foss@gmail.com \
--cc=afaerber@suse.de \
--cc=hsnaves@gmail.com \
--cc=kgene.kim@samsung.com \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=ruppi.kim@hardkernel.com \
--cc=t.dakhran@samsung.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).