From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Samsung boards for v3.2
Date: Tue, 20 Sep 2011 22:30:09 +0200 [thread overview]
Message-ID: <201109202230.09426.arnd@arndb.de> (raw)
In-Reply-To: <001a01cc76b8$208e52c0$61aaf840$%kim@samsung.com>
On Monday 19 September 2011, Kukjin Kim wrote:
> Please pull from:
> git://github.com/kgene/linux-samsung.git next-samsung-board
>
> As you see, the next-samsung-board includes new board, SMDK4212. Of course
> to support new SoC, EXYNOS4212 is required for it but current
> arch/arm/mach-exynos4 (ARCH_EXYNOS4) can support it so I merged it into
> next-samsung-board not next-samsung-soc and to support handling of cupid and
> rev. in Samsung stuff for it. As I remember, you said -soc branch of arm-soc
> is for adding new architecture like arch/arm/mach-xxxx.
>
> As a note, this includes samsung-fixes-2 which has been already pulled in
> your tree too.
Looks good. I had to apply the same atag_offset change to the new board
file that was done in all other branches as well.
Pulled into next/board. Thanks!
Arnd
next prev parent reply other threads:[~2011-09-20 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 10:37 [GIT PULL] Samsung boards for v3.2 Kukjin Kim
2011-09-20 20:30 ` Arnd Bergmann [this message]
2011-09-21 1:50 ` 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=201109202230.09426.arnd@arndb.de \
--to=arnd@arndb.de \
--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