Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp490935pxb; Wed, 27 Jan 2021 12:52:11 -0800 (PST) X-Google-Smtp-Source: ABdhPJxEIkjbwqS7xggW44kiwZQKIfcN5SA5uCNtFKQT6WD/E0JR23Wxsz3HJmHqkkiyGPcb+74E X-Received: by 2002:a05:6402:1152:: with SMTP id g18mr10961811edw.18.1611780730965; Wed, 27 Jan 2021 12:52:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611780730; cv=none; d=google.com; s=arc-20160816; b=Ru06LIn81cmBOQU2i4atAoJC/fRY1Sem27Pzj7sY9j30B0FNZ10aBB/VZnZ0mU+wHy gVkA8hRcbAXUGrmD0zf+xb+Rs8yg/ilWCDFry9fhIO6JbJWlrr2bXIJ/XsM55hCTR8rE Qxw1Fh5E/535Gocd0nH224ieQuXRZx8yGG2u1ZTsvqKjtoCagKEBLN14yWv2+NXf+CAL l07IG2PXl4262foFOMixZUtdzxVbgb3MRagaC1MhBvTFehbfz8egmz5fiH7FLNCNWLyJ jTzrXwCd+FDvbadvCSGdln5/IsG4z3mnS1CjlTT7R2PrVthX1J+eWvV/X0kO6dtWdRRt pIiQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=TV/IDv8UDDhdWqeq2vdMfhsfA66ls8W2Gh+7CnwYTgU=; b=CaER/OmT/Ymws+3fjnQoPzhsOHfIgb5r0d4+A+9vJpnOsCUfder8MuTD8tevlSW/f6 HlxfuMKYs5kC/lqrlKYEb5ujEURXs+XUX/ixkkAh25+HokLVBgR2bZiuY+JnWBAg6515 Q778yKFlgHW2Or/l0c+Gx3mIRk5poPR8LvJ8UN2wW9Bm0qHaP1uYREN+PLWIHKYyhha3 EOrVLNo2iwP57SBn+ha9L4IA54rMsRxI8IvlFMqAqn2SoyraYieOo0ApfueY97fZUVsN G4BaX379Y9om3dhmvRjV0YB+ghtNbcw+3u62Yow2tU3WAW+CsYMQ82QTZc8XQIfLYQDf j2Qw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id hc42si1268527ejc.750.2021.01.27.12.51.44; Wed, 27 Jan 2021 12:52:10 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233158AbhA0Dy6 (ORCPT + 99 others); Tue, 26 Jan 2021 22:54:58 -0500 Received: from szxga04-in.huawei.com ([45.249.212.190]:11602 "EHLO szxga04-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2392495AbhA0Bm4 (ORCPT ); Tue, 26 Jan 2021 20:42:56 -0500 Received: from DGGEMS407-HUB.china.huawei.com (unknown [172.30.72.58]) by szxga04-in.huawei.com (SkyGuard) with ESMTP id 4DQQll5dQ6z1607q; Wed, 27 Jan 2021 09:20:51 +0800 (CST) Received: from [127.0.0.1] (10.174.176.220) by DGGEMS407-HUB.china.huawei.com (10.3.19.207) with Microsoft SMTP Server id 14.3.498.0; Wed, 27 Jan 2021 09:21:54 +0800 Subject: Re: [PATCH v3 2/4] arm64: dts: correct vendor prefix hisi to hisilicon To: Arnd Bergmann CC: Philipp Zabel , Wei Xu , "Rob Herring" , linux-arm-kernel , devicetree , linux-kernel , Zhangfei Gao , Chen Feng , Manivannan Sadhasivam References: <20201208124641.1787-1-thunder.leizhen@huawei.com> <20201208124641.1787-3-thunder.leizhen@huawei.com> From: "Leizhen (ThunderTown)" Message-ID: Date: Wed, 27 Jan 2021 09:21:53 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.174.176.220] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2021/1/27 6:23, Arnd Bergmann wrote: > On Tue, Dec 8, 2020 at 1:46 PM Zhen Lei 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 >> Cc: Chen Feng >> Cc: Manivannan Sadhasivam > > 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 > > . >