From: Olof Johansson <olof@lixom.net>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: arm@kernel.org, 'Arnd Bergmann' <arnd@arndb.de>,
'Kevin Hilman' <khilman@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [GIT PULL 3rd 2/3] Samsung Exynos SoC updates for 3.16
Date: Thu, 29 May 2014 12:40:02 -0700 [thread overview]
Message-ID: <20140529194002.GG18481@quad.lixom.net> (raw)
In-Reply-To: <035701cf7897$6fb5e460$4f21ad20$@samsung.com>
On Mon, May 26, 2014 at 01:03:22PM +0900, Kukjin Kim wrote:
> The following changes since commit be1f7c8d7e2bc8b8c76846aa6f276e8d2ef8975a:
>
> cpufreq: exynos: Fix the compile error (2014-05-26 04:05:01 +0900)
>
> are available in the git repository at:
>
> http://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> tags/exynos-soc
>
> for you to fetch changes up to 455ae9aba2f05e77eaf1073b78e887b06f93a4fd:
>
> ARM: dts: Add device tree sources for exynos3250 (2014-05-26 05:32:02
> +0900)
>
> ----------------------------------------------------------------
> Exynos new SoCs support for v3.16
>
> - add support for exynos5260 SoC and exynos5260-xyref5260 board
> - add support for exynos5800 SoC and exynos5800-peach-pi board
> - add support for exynos3250 SoC
>
> Note that this branch is on top of tags/samsung-cleanup.
This branch mixes contents from what should be two branches: One quite short
one that just contains the code/Kconfig changes for the new SoCs. And the rest
(DTS/DTSI additions) should go in a DT branch.
Please respin as two separate branches. This will include respinning the
multiplatform branches too, etc, unfortunately. Please post fresh pull requests
for any respun/rebased branch.
-Olof
next prev parent reply other threads:[~2014-05-29 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 4:03 [GIT PULL 3rd 2/3] Samsung Exynos SoC updates for 3.16 Kukjin Kim
2014-05-29 19:40 ` Olof Johansson [this message]
2014-05-30 1:45 ` 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=20140529194002.GG18481@quad.lixom.net \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=kgene.kim@samsung.com \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.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