From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Arnd Bergmann' <arnd@arndb.de>, 'Olof Johansson' <olof@lixom.net>
Cc: 'Sachin Kamat' <sachin.kamat@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: RE: [PATCH 5/6] ARM: EXYNOS: Enable multi-platform build support
Date: Tue, 13 May 2014 13:37:33 +0900 [thread overview]
Message-ID: <065d01cf6e65$0e903dc0$2bb0b940$@samsung.com> (raw)
In-Reply-To: <201404222156.48432.arnd@arndb.de>
Arnd Bergmann wrote:
>
> On Tuesday 22 April 2014, Olof Johansson wrote:
> > I don't think there's a point in keeping this around. A
> > "single-platform" config is just enabling a single platform in the
> > config, it's not a specific option. I don't think any of the other
> > platforms use anything like this today.
>
> The only one doing that is shmobile, but only because they have
> some SoCs that are multiplatform capable and some that are not.
> This isn't the case for Exynos, so it should no longer be needed.
>
> When I originally created this patch 18 months ago, there were a
> number of drivers that broke when multiplatform got enabled.
> Now the cpufreq driver is the only one left, but it seems that
> it will make it for 3.16, and I wouldn't wait for it if it doesn't.
> Let's just do multiplatform-only.
>
In my position in S.LSI, I'd like to keep the current ARCH_EXYNOS4 and
EXYNOS5 because IMHO selecting each series would be helpful on real product,
multiplatform is available though. Additionally EXYNOS3 is being added.
It's true we can support exynos-multiplatform even though above options are
included...
Thanks,
Kukjin
next prev parent reply other threads:[~2014-05-13 4:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 9:28 [PATCH v2 0/6] Further cleanup and enable multiplat build Sachin Kamat
2014-04-15 9:28 ` [PATCH 1/6] ARM: EXYNOS: Remove duplicate lines in Makefile Sachin Kamat
2014-04-15 9:28 ` [PATCH 2/6] ARM: EXYNOS: Remove exynos_subsys registration Sachin Kamat
2014-04-15 9:28 ` [PATCH 3/6] ARM: EXYNOS: Migrate Exynos specific macros from plat to mach Sachin Kamat
2014-04-15 9:28 ` [PATCH 4/6] ARM: EXYNOS: Remove unnecessary inclusion of cpu.h Sachin Kamat
2014-04-15 9:28 ` [PATCH 5/6] ARM: EXYNOS: Enable multi-platform build support Sachin Kamat
2014-04-16 13:51 ` Tomasz Figa
2014-04-16 14:31 ` Arnd Bergmann
2014-04-16 14:48 ` Tomasz Figa
2014-04-16 14:55 ` Thomas Abraham
2014-04-16 14:58 ` Tomasz Figa
2014-04-16 18:14 ` Arnd Bergmann
2014-04-16 20:50 ` Mark Brown
2014-04-16 21:00 ` Arnd Bergmann
2014-04-22 3:06 ` Olof Johansson
2014-04-22 19:56 ` Arnd Bergmann
2014-05-13 4:37 ` Kukjin Kim [this message]
2014-05-13 9:15 ` Arnd Bergmann
2014-05-13 18:01 ` Olof Johansson
2014-05-14 4:33 ` Kukjin Kim
2014-04-15 9:28 ` [PATCH 6/6] ARM: multi_v7_defconfig: Enable Exynos platform Sachin Kamat
2014-04-16 13:51 ` [PATCH v2 0/6] Further cleanup and enable multiplat build Tomasz Figa
2014-05-04 15:35 ` Sachin Kamat
2014-05-12 22:30 ` Kukjin Kim
-- strict thread matches above, loose matches on Subject: below --
2014-04-10 8:24 [PATCH " Sachin Kamat
2014-04-10 8:24 ` [PATCH 5/6] ARM: EXYNOS: Enable multi-platform build support Sachin Kamat
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='065d01cf6e65$0e903dc0$2bb0b940$@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=sachin.kamat@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox