From: Catalin Marinas <catalin.marinas@arm.com>
To: Olof Johansson <olof@lixom.net>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Ilho Lee <ilho215.lee@samsung.com>,
Thomas Abraham <thomas.ab@samsung.com>
Subject: Re: [PATCH 2/3] arm64: Add Kconfig option for Samsung GH7 SoC family
Date: Wed, 12 Feb 2014 10:38:24 +0000 [thread overview]
Message-ID: <20140212103824.GF29702@arm.com> (raw)
In-Reply-To: <CAOesGMiWsWXkQkb-_VZGco0gKNZPsHf3ubR88y4Pt4-umk5_Ww@mail.gmail.com>
On Tue, Feb 11, 2014 at 11:39:27PM +0000, Olof Johansson wrote:
> On Mon, Feb 10, 2014 at 10:29 PM, Kukjin Kim <kgene.kim@samsung.com> wrote:
> > This patch adds support for Samsung GH7 SoC in arm64/Kconfig.
> >
> > Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
> > Cc: Catalin Marinas <catalin.marinas@arm.com>
>
> The overhead of building one more device tree isn't very large, and I
> don't see any other need to have a Kconfig entry per SoC at this time.
> It's of course up to Catalin, but you might just want to always
> compile all dts files instead.
For arm64, I thought of getting rid of ARCH_* Kconfig entries entirely,
only that I haven't heard any strong opinion either way (in which case
I'll do it, with a risk of single Image getting bigger and bigger and
people needing smaller Image can trim their .config).
--
Catalin
next prev parent reply other threads:[~2014-02-12 10:38 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 6:29 [PATCH 0/3] arm64: add new support Samsung GH7 SoC and SSDK board Kukjin Kim
2014-02-11 6:29 ` [PATCH 1/3] arm64: dts: add initial dts for Samsung GH7 SoC and SSDK-GH7 board Kukjin Kim
2014-02-11 18:15 ` Mark Rutland
2014-02-11 3:16 ` Kukjin Kim
2014-02-18 10:30 ` Mark Rutland
2014-02-24 23:56 ` Kukjin Kim
2014-02-11 23:36 ` Olof Johansson
2014-02-11 3:25 ` Kukjin Kim
2014-02-12 11:13 ` Marc Zyngier
2014-02-12 11:29 ` Mark Rutland
2014-02-12 11:40 ` Marc Zyngier
2014-02-11 3:03 ` Kukjin Kim
2014-02-11 6:29 ` [PATCH 2/3] arm64: Add Kconfig option for Samsung GH7 SoC family Kukjin Kim
2014-02-11 23:39 ` Olof Johansson
2014-02-12 10:38 ` Catalin Marinas [this message]
2014-02-12 16:25 ` Kumar Gala
2014-02-12 18:12 ` Catalin Marinas
2014-02-12 19:04 ` Kumar Gala
2014-02-12 19:14 ` Arnd Bergmann
2014-02-11 2:52 ` Kukjin Kim
2014-02-13 19:26 ` Olof Johansson
2014-02-14 17:06 ` Arnd Bergmann
2014-02-18 1:10 ` Kukjin Kim
2014-02-18 10:53 ` Arnd Bergmann
2014-02-18 16:16 ` Olof Johansson
2014-02-18 18:13 ` Arnd Bergmann
2014-02-18 19:52 ` John Stultz
2014-02-18 20:00 ` Olof Johansson
2014-02-18 20:06 ` John Stultz
2014-02-20 9:03 ` Olof Johansson
2014-02-20 11:22 ` Catalin Marinas
2014-02-20 12:07 ` Arnd Bergmann
2014-02-20 17:09 ` Olof Johansson
2014-02-20 18:58 ` Catalin Marinas
2014-02-25 0:19 ` Kukjin Kim
2014-02-25 0:20 ` Kukjin Kim
2014-02-25 0:10 ` Kukjin Kim
2014-02-18 16:40 ` Catalin Marinas
2014-02-13 20:08 ` Rob Herring
2014-02-13 20:19 ` Olof Johansson
2014-02-11 6:29 ` [PATCH 3/3] Documentation: DT: add new entry for Samsung GH7 SoC and SSDK board 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=20140212103824.GF29702@arm.com \
--to=catalin.marinas@arm.com \
--cc=ilho215.lee@samsung.com \
--cc=kgene.kim@samsung.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox