From: Arnd Bergmann <arnd@arndb.de>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: 'Olof Johansson' <olof@lixom.net>,
Kevin Hilman <khilman@linaro.org>,
arm@kernel.org,
"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 1/2] Samsung cleanup for 3.18
Date: Thu, 25 Sep 2014 23:24:24 +0200 [thread overview]
Message-ID: <201409252324.24297.arnd@arndb.de> (raw)
In-Reply-To: <5418BC87.8000306@samsung.com>
On Wednesday 17 September 2014, Kukjin Kim wrote:
> Samsung cleanup for 3.18
> - remove unused <mach/memory.h> in exynos
> - local <mach/regs-clock.h> for s5pv210
> - cleanup boot address calculate for exynos
> - remove separate restart code for s3c24xx
Pulled into next/cleanup, thanks!
Arnd
prev parent reply other threads:[~2014-09-25 21:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 22:41 [GIT PULL 1/2] Samsung cleanup for 3.18 Kukjin Kim
2014-09-25 21:24 ` Arnd Bergmann [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=201409252324.24297.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=kgene.kim@samsung.com \
--cc=khilman@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox