From: Olof Johansson <olof@lixom.net>
To: Kukjin Kim <kgene@kernel.org>
Cc: Kevin Hilman <khilman@linaro.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Mark Brown <broonie@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: Broken device trees for exynos in linux-next
Date: Thu, 22 Aug 2013 09:20:24 -0700 [thread overview]
Message-ID: <CAOesGMhSsWp1ECuGfoB1P4TmZzc-bbDET5DwwdbvvJfJ2k2xJw@mail.gmail.com> (raw)
In-Reply-To: <1c7e01ce9f1d$bf4967d0$3ddc3770$@org>
Kukjin,
On Thu, Aug 22, 2013 at 2:55 AM, Kukjin Kim <kgene@kernel.org> wrote:
> Yeah, it can be used for test. But there are many differences between
> exynos_defconfig and exynos5440_defconfig...PCIe, GbE, HugeTLB and KVM...so
> I'm still wondering how to handle it without other defconfig.
>
> Olof, do you still having objection for exynos5440_defconfig? If so, OK I
> will revert exynos5440_defconfig for now so that I could pull out the
> 'defconfig' branch to arm-soc for upcoming merge window. Then, let's discuss
> again :)
As far as I see it, you have two options:
1. Add the needed drivers to multi_v7_defconfig and use that for your platform.
2. Add them to both multi_v7_defconfig and exynos_defconfig.
Enabling the new drivers on exynos_defconfig does no harm.
I don't want to see a new defconfig for this.
-Olof
WARNING: multiple messages have this Message-ID (diff)
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: Broken device trees for exynos in linux-next
Date: Thu, 22 Aug 2013 09:20:24 -0700 [thread overview]
Message-ID: <CAOesGMhSsWp1ECuGfoB1P4TmZzc-bbDET5DwwdbvvJfJ2k2xJw@mail.gmail.com> (raw)
In-Reply-To: <1c7e01ce9f1d$bf4967d0$3ddc3770$@org>
Kukjin,
On Thu, Aug 22, 2013 at 2:55 AM, Kukjin Kim <kgene@kernel.org> wrote:
> Yeah, it can be used for test. But there are many differences between
> exynos_defconfig and exynos5440_defconfig...PCIe, GbE, HugeTLB and KVM...so
> I'm still wondering how to handle it without other defconfig.
>
> Olof, do you still having objection for exynos5440_defconfig? If so, OK I
> will revert exynos5440_defconfig for now so that I could pull out the
> 'defconfig' branch to arm-soc for upcoming merge window. Then, let's discuss
> again :)
As far as I see it, you have two options:
1. Add the needed drivers to multi_v7_defconfig and use that for your platform.
2. Add them to both multi_v7_defconfig and exynos_defconfig.
Enabling the new drivers on exynos_defconfig does no harm.
I don't want to see a new defconfig for this.
-Olof
next prev parent reply other threads:[~2013-08-22 16:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 16:43 Broken device trees for exynos in linux-next Olof Johansson
2013-08-15 16:43 ` Olof Johansson
2013-08-16 0:04 ` Kukjin Kim
2013-08-16 0:04 ` Kukjin Kim
2013-08-16 0:35 ` Mark Brown
2013-08-16 0:35 ` Mark Brown
2013-08-16 0:42 ` Mark Brown
2013-08-16 0:42 ` Mark Brown
2013-08-16 3:34 ` Padma Venkat
2013-08-16 3:34 ` Padma Venkat
2013-08-16 16:04 ` Olof Johansson
2013-08-16 16:04 ` Olof Johansson
2013-08-16 18:03 ` Mark Brown
2013-08-16 18:03 ` Mark Brown
2013-08-17 10:40 ` Kukjin Kim
2013-08-17 10:40 ` Kukjin Kim
2013-08-19 15:15 ` Kevin Hilman
2013-08-19 15:15 ` Kevin Hilman
2013-08-22 9:55 ` Kukjin Kim
2013-08-22 9:55 ` Kukjin Kim
2013-08-22 16:20 ` Olof Johansson [this message]
2013-08-22 16:20 ` 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=CAOesGMhSsWp1ECuGfoB1P4TmZzc-bbDET5DwwdbvvJfJ2k2xJw@mail.gmail.com \
--to=olof@lixom.net \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=kgene@kernel.org \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.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 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.