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-samsung-soc@vger.kernel.org,
"'Rafael J. Wysocki'" <rjw@sisk.pl>
Subject: Re: [GIT PULL] Samsung devel-2 for v3.6
Date: Sat, 21 Jul 2012 21:46:04 +0000 [thread overview]
Message-ID: <201207212146.04865.arnd@arndb.de> (raw)
In-Reply-To: <194f01cd65fe$7c865790$759306b0$%kim@samsung.com>
On Thursday 19 July 2012, Kukjin Kim wrote:
> Please pull it from:
> git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git next/devel-samsung-2
>
> The updating cpufreq for 1.7GHz of exynos5250 has been included in samsung tree because Rafael
> thought it was more related in samsung platform and I agreed. And it is including new
> exynos_defconfig for DT configuration of exynos4 and exynos5 together. The old exynos4_defconfig
> will be used for non-DT for a while and we will try to move on using exynos_defconfig for only DT.
> And others are adding G2D clock for exynos4x12 Socs.
>
I have pulled all three branches. The next/soc branch was getting pretty big now,
and I already started a late/soc branch for late stuff, so I put devel-2 into
late/soc. I also took the liberty to rebase it in order to split out the defconfig
change into a separate series that I applied to the defconfig branch.
Please confirm that this is ok. If the rebasing cases problems, I can undo that
and take all of devel-2 into late/soc.
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 devel-2 for v3.6
Date: Sat, 21 Jul 2012 21:46:04 +0000 [thread overview]
Message-ID: <201207212146.04865.arnd@arndb.de> (raw)
In-Reply-To: <194f01cd65fe$7c865790$759306b0$%kim@samsung.com>
On Thursday 19 July 2012, Kukjin Kim wrote:
> Please pull it from:
> git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git next/devel-samsung-2
>
> The updating cpufreq for 1.7GHz of exynos5250 has been included in samsung tree because Rafael
> thought it was more related in samsung platform and I agreed. And it is including new
> exynos_defconfig for DT configuration of exynos4 and exynos5 together. The old exynos4_defconfig
> will be used for non-DT for a while and we will try to move on using exynos_defconfig for only DT.
> And others are adding G2D clock for exynos4x12 Socs.
>
I have pulled all three branches. The next/soc branch was getting pretty big now,
and I already started a late/soc branch for late stuff, so I put devel-2 into
late/soc. I also took the liberty to rebase it in order to split out the defconfig
change into a separate series that I applied to the defconfig branch.
Please confirm that this is ok. If the rebasing cases problems, I can undo that
and take all of devel-2 into late/soc.
Arnd
next prev parent reply other threads:[~2012-07-21 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 22:33 [GIT PULL] Samsung devel-2 for v3.6 Kukjin Kim
2012-07-19 22:33 ` Kukjin Kim
2012-07-21 21:46 ` Arnd Bergmann [this message]
2012-07-21 21:46 ` Arnd Bergmann
2012-07-22 22:36 ` Kukjin Kim
2012-07-22 22:36 ` 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=201207212146.04865.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 \
--cc=rjw@sisk.pl \
/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.