From: Tomasz Figa <tomasz.figa@gmail.com>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Pankaj Dubey <pankaj.dubey@samsung.com>,
sunil joshi <joshi@samsung.com>,
Kukjin Kim <kgene.kim@samsung.com>,
Olof Johansson <olof@lixom.net>,
Rahul Sharma <r.sh.open@gmail.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Rahul Sharma <rahul.sharma@samsung.com>
Subject: Re: [PATCH v8 1/3] ARM: EXYNOS: initial board support for exynos5260 SoC
Date: Wed, 16 Apr 2014 10:10:15 +0200 [thread overview]
Message-ID: <534E3AE7.10907@gmail.com> (raw)
In-Reply-To: <CAK9yfHztqGWhUJ=PNc7L-epu48PkEM6=v6JFDZ1n52NBeOUB8w@mail.gmail.com>
On 16.04.2014 10:08, Sachin Kamat wrote:
> Hi Tomasz,
>
> On 16 April 2014 13:27, Tomasz Figa <tomasz.figa@gmail.com> wrote:
>> Hi Rahul,
>>
>>
>> On 16.04.2014 05:58, Rahul Sharma wrote:
>>>
>>> From: Pankaj Dubey <pankaj.dubey@samsung.com>
>>>
>>> This patch add basic arch side support for exynos5260 SoC.
>>>
>>> Signed-off-by: Pankaj Dubey <pankaj.dubey@samsung.com>
>>> Signed-off-by: Rahul Sharma <rahul.sharma@samsung.com>
>>> Reviewed-by: Tomasz Figa <t.figa@samsung.com>
>>> ---
>>> arch/arm/mach-exynos/Kconfig | 5 +++++
>>> 1 file changed, 5 insertions(+)
>>>
>>> diff --git a/arch/arm/mach-exynos/Kconfig b/arch/arm/mach-exynos/Kconfig
>>> index fc8bf18..bf4ed87 100644
>>> --- a/arch/arm/mach-exynos/Kconfig
>>> +++ b/arch/arm/mach-exynos/Kconfig
>>> @@ -84,6 +84,11 @@ config SOC_EXYNOS5250
>>> help
>>> Enable EXYNOS5250 SoC support
>>>
>>> +config SOC_EXYNOS5260
>>> + bool "SAMSUNG EXYNOS5260"
>>> + default y
>>> + depends on ARCH_EXYNOS5
>>> +
>>> config SOC_EXYNOS5420
>>> bool "SAMSUNG EXYNOS5420"
>>> default y
>>>
>>
>> Is this patch necessary now? After Sachin's consolidation series there are
>> no per SoC entries anymore.
>
> Kukjin still wanted individual SoCs to be selectable. Please refer [1].
>
> [1] http://www.spinics.net/lists/devicetree/msg27040.html
I don't think any valid reason was presented there. Features in code
should not be selected using #ifdef CONFIG_ anymore, so I don't really
see any reason to not proceed with this consolidation. Olof, Arnd?
Best regards,
Tomasz
next prev parent reply other threads:[~2014-04-16 8:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 3:58 [PATCH v8 0/3] exynos: arch: add support for exynos5260 SoC Rahul Sharma
2014-04-16 3:58 ` [PATCH v8 1/3] ARM: EXYNOS: initial board " Rahul Sharma
2014-04-16 7:57 ` Tomasz Figa
2014-04-16 8:08 ` Sachin Kamat
2014-04-16 8:10 ` Tomasz Figa [this message]
2014-04-22 22:36 ` Kukjin Kim
2014-04-24 19:09 ` Rahul Sharma
2014-04-26 11:01 ` Kukjin Kim
2014-04-28 6:33 ` Rahul Sharma
2014-05-08 17:37 ` Tomasz Figa
2014-04-16 3:58 ` [PATCH v8 2/3] ARM: dts: add dts files " Rahul Sharma
2014-04-22 22:38 ` Kukjin Kim
2014-04-16 3:58 ` [PATCH v8 3/3] ARM: dts: add dts files for xyref5260 board Rahul Sharma
2014-04-16 4:25 ` [PATCH v8 0/3] exynos: arch: add support for exynos5260 SoC 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=534E3AE7.10907@gmail.com \
--to=tomasz.figa@gmail.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=joshi@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=pankaj.dubey@samsung.com \
--cc=r.sh.open@gmail.com \
--cc=rahul.sharma@samsung.com \
--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;
as well as URLs for NNTP newsgroup(s).