From: Arnd Bergmann <arnd@arndb.de>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: 'Olof Johansson' <olof@lixom.net>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>
Subject: Re: [GIT PULL] Samsung boards update for v3.5
Date: Mon, 14 May 2012 20:03:27 +0000 [thread overview]
Message-ID: <201205142003.27537.arnd@arndb.de> (raw)
In-Reply-To: <4FAF0326.8000408@samsung.com>
On Sunday 13 May 2012, Kukjin Kim wrote:
> Hi Arnd, Olof,
>
> Please pull Samsung boards update for v3.5.
> git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> next/board-samsung
>
> As there were discussions, some exynos4 boards have been updated because
> current dt cannot support all features for current board files on exynos4.
>
> Note, this should be merged after next/devel-samsung because some
> platform devices are defined in that.
>
> If any problems, please let me know.
Pulled into next/boards now.
Since we have not pulled the next/devel-samsung branch yet, and that branch
depends on the sysmmu branch, the dependencies won't easily get fulfilled.
A test build of exynos4_defconfig showed that there is at least no build
time problem.
What is the dependency you are referring to?
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Samsung boards update for v3.5
Date: Mon, 14 May 2012 20:03:27 +0000 [thread overview]
Message-ID: <201205142003.27537.arnd@arndb.de> (raw)
In-Reply-To: <4FAF0326.8000408@samsung.com>
On Sunday 13 May 2012, Kukjin Kim wrote:
> Hi Arnd, Olof,
>
> Please pull Samsung boards update for v3.5.
> git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> next/board-samsung
>
> As there were discussions, some exynos4 boards have been updated because
> current dt cannot support all features for current board files on exynos4.
>
> Note, this should be merged after next/devel-samsung because some
> platform devices are defined in that.
>
> If any problems, please let me know.
Pulled into next/boards now.
Since we have not pulled the next/devel-samsung branch yet, and that branch
depends on the sysmmu branch, the dependencies won't easily get fulfilled.
A test build of exynos4_defconfig showed that there is at least no build
time problem.
What is the dependency you are referring to?
Arnd
next prev parent reply other threads:[~2012-05-14 20:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-13 0:41 [GIT PULL] Samsung boards update for v3.5 Kukjin Kim
2012-05-13 0:41 ` Kukjin Kim
2012-05-14 20:03 ` Arnd Bergmann [this message]
2012-05-14 20:03 ` Arnd Bergmann
2012-05-15 8:55 ` Kukjin Kim
2012-05-15 8:55 ` 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=201205142003.27537.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=olof@lixom.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.