[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAfSe-vuSgwH2PHQdYLyfJ+KZ0C8a7D6Ry=mHaBrjpbuksaKvQ@mail.gmail.com>
Date: Fri, 16 Jan 2015 19:50:18 +0800
From: Lyra Zhang <zhang.lyra@...il.com>
To: Mark Rutland <mark.rutland@....com>
Cc: Chunyan Zhang <chunyan.zhang@...eadtrum.com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"arnd@...db.de" <arnd@...db.de>,
"gnomes@...rguk.ukuu.org.uk" <gnomes@...rguk.ukuu.org.uk>,
"broonie@...nel.org" <broonie@...nel.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
Pawel Moll <Pawel.Moll@....com>,
"ijc+devicetree@...lion.org.uk" <ijc+devicetree@...lion.org.uk>,
"galak@...eaurora.org" <galak@...eaurora.org>,
Will Deacon <Will.Deacon@....com>,
Catalin Marinas <Catalin.Marinas@....com>,
"jslaby@...e.cz" <jslaby@...e.cz>,
"jason@...edaemon.net" <jason@...edaemon.net>,
"heiko@...ech.de" <heiko@...ech.de>,
"florian.vaussard@...l.ch" <florian.vaussard@...l.ch>,
"andrew@...n.ch" <andrew@...n.ch>,
"rrichter@...ium.com" <rrichter@...ium.com>,
"hytszk@...il.com" <hytszk@...il.com>,
"grant.likely@...aro.org" <grant.likely@...aro.org>,
"antonynpavlov@...il.com" <antonynpavlov@...il.com>,
"Joel.Schopp@....com" <Joel.Schopp@....com>,
"suravee.suthikulpanit@....com" <suravee.suthikulpanit@....com>,
"shawn.guo@...aro.org" <shawn.guo@...aro.org>,
"jorge.ramirez-ortiz@...aro.org" <jorge.ramirez-ortiz@...aro.org>,
"lee.jones@...aro.org" <lee.jones@...aro.org>,
"orsonzhai@...il.com" <orsonzhai@...il.com>,
"geng.ren@...eadtrum.com" <geng.ren@...eadtrum.com>,
"zhizhou.zhang@...eadtrum.com" <zhizhou.zhang@...eadtrum.com>,
"lanqing.liu@...eadtrum.com" <lanqing.liu@...eadtrum.com>,
"wei.qiao@...eadtrum.com" <wei.qiao@...eadtrum.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>,
"linux-api@...r.kernel.org" <linux-api@...r.kernel.org>
Subject: Re: [PATCH v5 4/5] arm64: Add support for Spreadtrum's Sharkl64
Platform in Kconfig and defconfig
Hi, Mark
On Fri, Jan 16, 2015 at 6:48 PM, Mark Rutland <mark.rutland@....com> wrote:
> On Fri, Jan 16, 2015 at 10:00:10AM +0000, Chunyan Zhang wrote:
>> From: Zhizhou Zhang <zhizhou.zhang@...eadtrum.com>
>>
>> Adds support for Spreadtrum's SoC Platform in the arm64 Kconfig and
>> defconfig files.
>>
>> Signed-off-by: Zhizhou Zhang <zhizhou.zhang@...eadtrum.com>
>> Signed-off-by: Orson Zhai <orson.zhai@...eadtrum.com>
>> Signed-off-by: Chunyan Zhang <chunyan.zhang@...eadtrum.com>
>> ---
>> arch/arm64/Kconfig | 5 +++++
>> arch/arm64/configs/defconfig | 1 +
>> 2 files changed, 6 insertions(+)
>>
>> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
>> index b1f9a20..885c1f4 100644
>> --- a/arch/arm64/Kconfig
>> +++ b/arch/arm64/Kconfig
>> @@ -153,6 +153,11 @@ config ARCH_SEATTLE
>> help
>> This enables support for AMD Seattle SOC Family
>>
>> +config ARCH_SPRD
>
> This should presumably be ARCH_SHARKL64, so you can add other SoC
> families later. The other entries in here are already formatted that
> way.
>
> I wonder if we should have these of the form ARCH_${VENDOR}_${FAMILY}
> (e.g. ARCH_SPRD_SHARKL64) rather than just ARCH_${FAMILY} to save
> ourselves from name conflicts in future (and to make it easier to grep
> for a particular vendor's config options).
>
actually we've discussed this question before[1], and I think Arnd's
suggestion is suitable for our case, so I changed this to use
ARCH_SPRD instead of ARCH_SHARKL64.
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-November/306246.html
anyway, thank you very much!
Chunyan
>> + bool "Spreadtrum SoC platform"
>
> bool "Spreadtrun Sharkl64 SoC Family"
>
>> + help
>> + Support for Spreadtrum ARM based SoCs
>
>
> Support for the Spreadtrum Sharkl64 SoC family.
>
> Thanks,
> Mark.
>
>> +
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists