From: Kukjin Kim <kgene.kim@samsung.com>
To: Arnd Bergmann <arnd@arndb.de>, 'Olof Johansson' <olof@lixom.net>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Thomas Abraham <thomas.ab@samsung.com>
Subject: [GIT PULL] Late Samsung stuff (v3) for v3.10
Date: Fri, 26 Apr 2013 01:42:16 +0900 [thread overview]
Message-ID: <51795CE8.2060105@samsung.com> (raw)
The following changes since commit 59a7bbf75442ea439a4d3b7993ad87023e406063:
ARM: dts: add PDMA0 changes for exynos5440 (2013-04-09 01:39:27 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
tags/late-exynos-v3-for-v3.10
for you to fetch changes up to 096ee6adcfb79a13ae04150023725c8a67e00ae8:
ARM: dts: Add chip-id controller node on Exynos4/5 SoC (2013-04-26
01:21:44 +0900)
----------------------------------------------------------------
This allows that device tree enables platform to setup a runtime IO
mapping for the chip id
----------------------------------------------------------------
Thomas Abraham (2):
ARM: EXYNOS: Create virtual I/O mapping for Chip-ID controller
using device tree
ARM: dts: Add chip-id controller node on Exynos4/5 SoC
arch/arm/boot/dts/exynos4.dtsi | 5 ++++
arch/arm/boot/dts/exynos5250.dtsi | 5 ++++
arch/arm/mach-exynos/common.c | 53
+++++++++++++++++++--------------
arch/arm/mach-exynos/include/mach/map.h | 1 -
4 files changed, 40 insertions(+), 24 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Late Samsung stuff (v3) for v3.10
Date: Fri, 26 Apr 2013 01:42:16 +0900 [thread overview]
Message-ID: <51795CE8.2060105@samsung.com> (raw)
The following changes since commit 59a7bbf75442ea439a4d3b7993ad87023e406063:
ARM: dts: add PDMA0 changes for exynos5440 (2013-04-09 01:39:27 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
tags/late-exynos-v3-for-v3.10
for you to fetch changes up to 096ee6adcfb79a13ae04150023725c8a67e00ae8:
ARM: dts: Add chip-id controller node on Exynos4/5 SoC (2013-04-26
01:21:44 +0900)
----------------------------------------------------------------
This allows that device tree enables platform to setup a runtime IO
mapping for the chip id
----------------------------------------------------------------
Thomas Abraham (2):
ARM: EXYNOS: Create virtual I/O mapping for Chip-ID controller
using device tree
ARM: dts: Add chip-id controller node on Exynos4/5 SoC
arch/arm/boot/dts/exynos4.dtsi | 5 ++++
arch/arm/boot/dts/exynos5250.dtsi | 5 ++++
arch/arm/mach-exynos/common.c | 53
+++++++++++++++++++--------------
arch/arm/mach-exynos/include/mach/map.h | 1 -
4 files changed, 40 insertions(+), 24 deletions(-)
next reply other threads:[~2013-04-25 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 16:42 Kukjin Kim [this message]
2013-04-25 16:42 ` [GIT PULL] Late Samsung stuff (v3) for v3.10 Kukjin Kim
2013-04-28 7:09 ` Kukjin Kim
2013-04-28 7:09 ` Kukjin Kim
2013-04-28 19:26 ` Olof Johansson
2013-04-28 19:26 ` 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=51795CE8.2060105@samsung.com \
--to=kgene.kim@samsung.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=thomas.ab@samsung.com \
/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.