linux-kernel - Re: [PATCH v2 3/9] 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] [day] [month] [year] [list]

Date:	Thu, 10 Dec 2015 09:25:56 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	linux-arm-kernel@...ts.infradead.org
Cc:	xuejiancheng <xuejiancheng@...wei.com>, suwenping@...ilicon.com,
	khilman@...aro.org, linux@....linux.org.uk,
	linux-kernel@...r.kernel.org, xuwei5@...ilicon.com,
	yanhaifeng@...ilicon.com, ml.yang@...ilicon.com,
	bintian.wang@...wei.com, gaofei@...ilicon.com,
	haojian.zhuang@...aro.org, olof@...om.net, zhangfei.gao@...aro.org,
	yanghongwei@...ilicon.com
Subject: Re: [PATCH v2 3/9] ARM: hisi: enable Hi3519 soc

On Thursday 10 December 2015 14:13:46 xuejiancheng wrote:
> 
> On 2015/12/9 23:32, Arnd Bergmann wrote:
> > On Tuesday 08 December 2015 11:03:20 xuejiancheng wrote:
> >>>>

> >>> Yes. It's correct. They may share some IP blocks. But they may be very different
> >>> from the new one for the arch code. I also don't think it's a good idea to make
> >>> them share the same name.
> >>
> >> I will use ARCH_HISI instead of ARCH_HI3519.
> >>
> >>
> > 
> > Do you mean you want to remove the other options as well?
> > 
> > We should do this consistently at least within the Kconfig file.
> 
> I think it is ideal if we can do that.  But I won't change it in HI3519 soc patch.
> 
> I will just use ARCH_HISI for HI3519 this time.
> 

Ok, sounds good.

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