Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Olof Johansson' <olof@lixom.net>
Cc: arm@kernel.org, 'Arnd Bergmann' <arnd@arndb.de>,
	'Kevin Hilman' <khilman@linaro.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org
Subject: RE: [GIT PULL 4th 1/2] Samsung Exynos multiplatform for 3.16
Date: Tue, 27 May 2014 09:04:46 +0900	[thread overview]
Message-ID: <00ed01cf793f$4722d780$d5688680$@samsung.com> (raw)
In-Reply-To: <CAOesGMiM=Yc__EoWUPwyV3YRuQ83CSK8v8W==yt2Z9zoPNSwRA@mail.gmail.com>

Olof Johansson wrote:
> 
> On Mon, May 26, 2014 at 3:12 PM, Kukjin Kim <kgene.kim@samsung.com> wrote:
> > Hi Arnd, Olof, Kevin
> >
> > Sorry for late support multiplatform on exynos and now it's possible.
> Thanks
> > for many guys' effort and time :-)
> >
> > BRs,
> > Kukjin
> >
> > The following changes since commit
> dfacdfef06090ca0c131f45dfd3f3ca3452a8ed3:
> >
> >   Merge branch 'v3.16-next/dt-samsung' into v3.16-next/multiplatform
> > (2014-05-26 06:19:01 +0900)
> >
> > are available in the git repository at:
> >
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> > tags/exynos-multiplatform
> >
> > for you to fetch changes up to 43baa7dcb5fa0c95b1e443d2a739c14de1fbbe07:
> >
> >   cpufreq: exynos: Fix driver compilation with ARCH_MULTIPLATFORM
> > (2014-05-27 06:22:53 +0900)
> >
> > ----------------------------------------------------------------
> > Exynos mutiplatform support for 3.16
> >
> > Here is enabling the exynos platform as part of a multiplatform
> > kernel. This is including ARCH_EXYNOS related Kconfig entries
> > consolidation and update multi_v7_defconfig accordingly. And
> > fixes exynos-cpufreq driver compilation with ARCH_MULTIPLATFORM.
> >
> > Note that this is based on tags/exynos-soc. And tags/samsung-dt,
> > tags/samsung-clk are merged on top of that.
> >
> > ----------------------------------------------------------------
> > Arnd Bergmann (1):
> >       ARM: EXYNOS: Enable multi-platform build support
> >
> > Sachin Kamat (2):
> >       ARM: EXYNOS: Consolidate Kconfig entries
> >       ARM: multi_v7_defconfig: Enable Exynos platform
> >
> > Tomasz Figa (1):
> >       cpufreq: exynos: Fix driver compilation with ARCH_MULTIPLATFORM
> >
> >  arch/arm/Kconfig                     | 20 ---------
> >  arch/arm/configs/multi_v7_defconfig  | 12 ++++++
> 
> Please send multi_v7_defconfig updates as patches to arm@kernel.org,
> and don't include them in branches. They often conflict and we want to
> apply them directly for that reason.
> 
Oh, I see.

So please kindly ignore this (4th) pull-request 1/2 and 2/2 for samsung-3.16, because 2/2 is based on this (1/2).

I will re-sort them out then will send it tonight in my time. Unfortunately I can't push anything in my office...

Thanks,
Kukjin

      reply	other threads:[~2014-05-27  0:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26 22:12 [GIT PULL 4th 1/2] Samsung Exynos multiplatform for 3.16 Kukjin Kim
2014-05-26 22:29 ` Olof Johansson
2014-05-27  0:04   ` Kukjin Kim [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='00ed01cf793f$4722d780$d5688680$@samsung.com' \
    --to=kgene.kim@samsung.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --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