[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aaf6ec27-b2cb-6e29-3c73-36c5c34b34e4@huawei.com>
Date: Wed, 27 Jan 2021 09:21:53 +0800
From: "Leizhen (ThunderTown)" <thunder.leizhen@...wei.com>
To: Arnd Bergmann <arnd@...nel.org>
CC: Philipp Zabel <p.zabel@...gutronix.de>,
Wei Xu <xuwei5@...ilicon.com>,
"Rob Herring" <robh+dt@...nel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
devicetree <devicetree@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Zhangfei Gao <zhangfei.gao@...aro.org>,
Chen Feng <puck.chen@...ilicon.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
Subject: Re: [PATCH v3 2/4] arm64: dts: correct vendor prefix hisi to
hisilicon
On 2021/1/27 6:23, Arnd Bergmann wrote:
> On Tue, Dec 8, 2020 at 1:46 PM Zhen Lei <thunder.leizhen@...wei.com> wrote:
>>
>> The vendor prefix of "Hisilicon Limited" is "hisilicon", it is clearly
>> stated in "vendor-prefixes.yaml".
>>
>> Fixes: 35ca8168133c ("arm64: dts: Add dts files for Hisilicon Hi3660 SoC")
>> Fixes: dd8c7b78c11b ("arm64: dts: Add devicetree for Hisilicon Hi3670 SoC")
>> Signed-off-by: Zhen Lei <thunder.leizhen@...wei.com>
>> Cc: Chen Feng <puck.chen@...ilicon.com>
>> Cc: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
>
> I see this change in the pull request I got, but I'm a bit worried about the
> incompatible binding change. Wouldn't the correct path forward be to
> list both the correct and the incorrect properties, both in the dts file
> and in the driver that interprets the properties?
Hi, Arnd:
This is one of the patch series. The other three patches have been applied by Philipp Zabel and are currently in linux-next.
https://lkml.org/lkml/2020/12/10/697
>
> The binding file in this case would need to list the old name as deprecated,
> though I'm not sure how that would work without causing a warning about
> the unknown vendor prefix.
>
> Arnd
>
> .
>
Powered by blists - more mailing lists