From: Arnd Bergmann <arnd@arndb.de>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: kgene.kim@samsung.com, t.figa@samsung.com,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/4] Consolidate Exynos machine code
Date: Wed, 19 Mar 2014 14:29:11 +0100 [thread overview]
Message-ID: <201403191429.11721.arnd@arndb.de> (raw)
In-Reply-To: <1395231957-22032-1-git-send-email-sachin.kamat@linaro.org>
On Wednesday 19 March 2014, Sachin Kamat wrote:
> This patch series consolidates the Exynos machine code and common
> code into a single file to avoid code duplication and introduces
> generic compatible strings for Exynos4 and 5 SoC series.
>
> Complete discussion and motivation for this series is found here:
> http://comments.gmane.org/gmane.linux.kernel.samsung-soc/27268
>
> This series is based on the latest linux-next and depends on
> 1. Tomasz Figa's PM consolidation series 1 and 2
> 2. Patch: ARM: SAMSUNG: Reorganize calls to reserve memory for MFC
> http://www.spinics.net/lists/linux-samsung-soc/msg25501.html
> 3. Patch: ARM: EXYNOS: Add support to reserve memory for MFC-v7
> http://www.spinics.net/lists/arm-kernel/msg315940.html
> 4. Kconfig and CPU init Consolidation series
> http://article.gmane.org/gmane.linux.kernel.samsung-soc/28216
Acked-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2014-03-19 13:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 12:25 [PATCH 0/4] Consolidate Exynos machine code Sachin Kamat
2014-03-19 12:25 ` [PATCH 1/4] ARM: SAMSUNG: Introduce generic Exynos4 and 5 helpers Sachin Kamat
2014-03-19 12:25 ` [PATCH 2/4] ARM: EXYNOS: Consolidate Exynos4 and 5 machine files Sachin Kamat
2014-03-19 12:25 ` [PATCH 3/4] ARM: EXYNOS: Add generic compatible strings Sachin Kamat
2014-03-19 12:25 ` [PATCH 4/4] ARM: dts: Update Exynos DT files with " Sachin Kamat
2014-03-19 13:29 ` Arnd Bergmann [this message]
2014-03-20 2:06 ` [PATCH 0/4] Consolidate Exynos machine code Kukjin Kim
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=201403191429.11721.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=sachin.kamat@linaro.org \
--cc=t.figa@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