From: Olof Johansson <olof@lixom.net>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Kevin Hilman <khilman@linaro.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>,
arm@kernel.org
Subject: Re: [GIT PULL 1/6] Samsung cleanup for v3.13
Date: Sun, 27 Oct 2013 21:33:11 -0700 [thread overview]
Message-ID: <20131028043311.GG22890@quad.lixom.net> (raw)
In-Reply-To: <526455CB.6050507@samsung.com>
On Mon, Oct 21, 2013 at 07:14:35AM +0900, Kukjin Kim wrote:
> The following changes since commit 4a10c2ac2f368583138b774ca41fac4207911983:
>
> Linux 3.12-rc2 (2013-09-23 15:41:09 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> tags/samsung-cleanup
>
> for you to fetch changes up to ae3c5d74ea0d5e2f1c32c527e5de36c7614525af:
>
> ARM: EXYNOS: remove CONFIG_MACH_EXYNOS[4, 5]_DT config options
> (2013-10-21 06:35:47 +0900)
Thanks, pulled into next/cleanup. Trivial add/add conflict when merging
into for-next due to the 64xx DT platform, no big deal.
-Olof
WARNING: multiple messages have this Message-ID (diff)
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/6] Samsung cleanup for v3.13
Date: Sun, 27 Oct 2013 21:33:11 -0700 [thread overview]
Message-ID: <20131028043311.GG22890@quad.lixom.net> (raw)
In-Reply-To: <526455CB.6050507@samsung.com>
On Mon, Oct 21, 2013 at 07:14:35AM +0900, Kukjin Kim wrote:
> The following changes since commit 4a10c2ac2f368583138b774ca41fac4207911983:
>
> Linux 3.12-rc2 (2013-09-23 15:41:09 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> tags/samsung-cleanup
>
> for you to fetch changes up to ae3c5d74ea0d5e2f1c32c527e5de36c7614525af:
>
> ARM: EXYNOS: remove CONFIG_MACH_EXYNOS[4, 5]_DT config options
> (2013-10-21 06:35:47 +0900)
Thanks, pulled into next/cleanup. Trivial add/add conflict when merging
into for-next due to the 64xx DT platform, no big deal.
-Olof
next prev parent reply other threads:[~2013-10-28 4:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-20 22:14 [GIT PULL 1/6] Samsung cleanup for v3.13 Kukjin Kim
2013-10-20 22:14 ` Kukjin Kim
2013-10-28 4:33 ` Olof Johansson [this message]
2013-10-28 4:33 ` Olof Johansson
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=20131028043311.GG22890@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 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.