linux-kernel - Re: [PATCH 2/5] ARM: hisi: enable Hi3519 soc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 30 Nov 2015 16:02:37 -0800
From:	Kevin Hilman <khilman@...nel.org>
To:	Jiancheng Xue <xuejiancheng@...wei.com>
Cc:	<linux@....linux.org.uk>, <arnd@...db.de>, <olof@...om.net>,
	<xuwei5@...ilicon.com>, <haojian.zhuang@...aro.org>,
	<zhangfei.gao@...aro.org>, <bintian.wang@...wei.com>,
	<linux-arm-kernel@...ts.infradead.org>,
	<linux-kernel@...r.kernel.org>, <linuxarm@...wei.com>,
	<yanhaifeng@...ilicon.com>, <yanghongwei@...ilicon.com>,
	<suwenping@...ilicon.com>, <ml.yang@...ilicon.com>
Subject: Re: [PATCH 2/5] ARM: hisi: enable Hi3519 soc

Jiancheng Xue <xuejiancheng@...wei.com> writes:

> Hi3519 SOC is mainly used for ip camera and sport dv
> solutions.
>
> Signed-off-by: Jiancheng Xue <xuejiancheng@...wei.com>
> ---
>  arch/arm/mach-hisi/Kconfig     | 9 +++++++++
>  arch/arm/mach-hisi/hisilicon.c | 9 +++++++++
>  2 files changed, 18 insertions(+)
>
> diff --git a/arch/arm/mach-hisi/Kconfig b/arch/arm/mach-hisi/Kconfig
> index 83061ad..6bb822c 100644
> --- a/arch/arm/mach-hisi/Kconfig
> +++ b/arch/arm/mach-hisi/Kconfig
> @@ -48,6 +48,15 @@ config ARCH_HIX5HD2
>  	select PINCTRL_SINGLE
>  	help
>  	  Support for Hisilicon HIX5HD2 SoC family
> +
> +config ARCH_HI3519

Please keep these sorted alphabetically.

Speaking of which, there is already an existing ARCH_HI3xxx entry.
Should this be included in that family?   If not, maybe the HI3xxx
should be renamed HI36xx ?

Kevin
--
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/