Received: by 2002:a05:6a10:144:0:0:0:0 with SMTP id 4csp1074602pxw; Sat, 9 Apr 2022 10:19:50 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxCnDS5duYzJ3sHQtkMuiw7JgW6L6SARXdHXcafxUURBLANmUNb/N909V/WXufRyWCGrv+Y X-Received: by 2002:a50:cd8c:0:b0:41c:bb5a:1c7b with SMTP id p12-20020a50cd8c000000b0041cbb5a1c7bmr24607176edi.351.1649524790680; Sat, 09 Apr 2022 10:19:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1649524790; cv=none; d=google.com; s=arc-20160816; b=QMLz9whhGA0vJpsnd0ZtrSqkwZBQF08Iq/uVYbyGe27Mqq/r+kltcQb+hGpFatUi/y Hj63wXLORTdEe5tsMSGJ1egbpgPeab1pHjcevO5hhjdlI/jrfJPFqMCEnuc98f1nVIJo fWAgIUE3HOx+UyAI51CsGvwgqvWN3RgXQPhLM1IlpLgjv55MYe9BgdKq9dQ1MOA7VkbJ xyheJd2nkCtM0gJrF1W4T8U0M9ZOQjGQy1iiZFcDIk5Is2WhDmOLLlouOIHljU/JD1xR IKy+F05QCvAeD4f/Nnf9w6Dj/mlXfASJkExMQV3abTmL4pjq06cFjZ36DgHHZgKxf/Qh PkIA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:to:references:message-id :content-transfer-encoding:cc:date:in-reply-to:from:subject :mime-version:dkim-signature; bh=kuxzjjranCHRLMmIxWWOWvmF7G3BXhuDOS6JbTTDhsk=; b=KHM3XigxzqEdQUG/pj8ZnmgSw4DWjlSwN+j4NxKAVf0jen4KskeYBO2VldnZgWMHyX HSj6EmqazVOlWYrA2MdgiNKicCtGTUxBu137Ghnp+mfHey6T2kbF7LBA/mZc44lJAkqG K+tjwCZKVdT7bl6TieI3In0XXZxuD1pHBQdHT1ehDtgikjfem5nj2YJSF7TZF0/BUXfn wNhSielkdmYy7faoi7yLbm8knDpyCz1HxM4GFMobmes+l/yBc01tjj3l8yWMvYZ3lecN d9Ds0xggnbMkKgGwE9I0772/sKIsrbare/CeeJDoL+q3DaU/doSb5FIawN9w2f3KHWvS N7lQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@goldelico.com header.s=strato-dkim-0002 header.b=Sz6ScZrd; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id lo10-20020a170906fa0a00b006e5fcf81b06si3193684ejb.134.2022.04.09.10.19.25; Sat, 09 Apr 2022 10:19:50 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@goldelico.com header.s=strato-dkim-0002 header.b=Sz6ScZrd; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241851AbiDING5 (ORCPT + 99 others); Sat, 9 Apr 2022 09:06:57 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49834 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230331AbiDING4 (ORCPT ); Sat, 9 Apr 2022 09:06:56 -0400 Received: from mo4-p02-ob.smtp.rzone.de (mo4-p02-ob.smtp.rzone.de [85.215.255.82]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8FF721959F0; Sat, 9 Apr 2022 06:04:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1649509485; s=strato-dkim-0002; d=goldelico.com; h=To:References:Message-Id:Cc:Date:In-Reply-To:From:Subject:Cc:Date: From:Subject:Sender; bh=kuxzjjranCHRLMmIxWWOWvmF7G3BXhuDOS6JbTTDhsk=; b=Sz6ScZrdCGeVafipGta4IzpIHSyr4eSTpTze0cS13tWuBJzHF4BgHvBsVtAA4wGCZ2 +ONEmQz+WhsU79ApqYUHJMpguC1Y/K5qceYAR13veELo3PlcKotLFs87JgSVmzdCNClq w30wgaOALTw8/sfmDA63+b5Gvcd2DmJ1GhtRK9Y31wm4tf41hfCyEl0IhnixaQsbfGIM +Bwac1oYK6EGQOXn8e5R7HTStVV4yMzUPMDL95z/k/XWaehlEAWfjRL2wgQRb0BxjBq4 110lq/aEt0/NTiFJXS9uaIVAQWfUp5ri+iq9lk+dUEODPIHPUKBIEhbMXTvhBEcfbYJW GYvg== Authentication-Results: strato.com; dkim=none X-RZG-AUTH: ":JGIXVUS7cutRB/49FwqZ7WcJeFKiMgPgp8VKxflSZ1P34KBj7wpz8NIGH/jrwDepmg==" X-RZG-CLASS-ID: mo00 Received: from imac.fritz.box by smtp.strato.de (RZmta 47.42.2 DYNA|AUTH) with ESMTPSA id k708cfy39D4juU7 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve X9_62_prime256v1 with 256 ECDH bits, eq. 3072 bits RSA)) (Client did not present a certificate); Sat, 9 Apr 2022 15:04:45 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\)) Subject: Re: [PATCH 05/18] MIPS: DTS: jz4780: fix pinctrl as reported by dtbscheck From: "H. Nikolaus Schaller" In-Reply-To: Date: Sat, 9 Apr 2022 15:04:44 +0200 Cc: Rob Herring , Paul Cercueil , Thomas Bogendoerfer , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-mips@vger.kernel.org, letux-kernel@openphoenux.org Content-Transfer-Encoding: quoted-printable Message-Id: <530E0F7F-FC03-45DD-BF87-D049D3108AD3@goldelico.com> References: <1941bc4ed553b27f399ad00ea61ff2b0237d14e3.1649443080.git.hns@goldelico.com> To: Krzysztof Kozlowski X-Mailer: Apple Mail (2.3445.104.21) X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_NONE, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Am 09.04.2022 um 13:13 schrieb Krzysztof Kozlowski = : >=20 > On 08/04/2022 20:37, H. Nikolaus Schaller wrote: >> arch/mips/boot/dts/ingenic/ci20.dtb: pin-controller@10010000: = $nodename:0: 'pin-controller@10010000' does not match = '^(pinctrl|pinmux)(@[0-9a-f]+)?$' >> =46rom schema: = Documentation/devicetree/bindings/pinctrl/ingenic,pinctrl.yaml >>=20 >> Signed-off-by: H. Nikolaus Schaller >> --- >> arch/mips/boot/dts/ingenic/jz4780.dtsi | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >>=20 >> diff --git a/arch/mips/boot/dts/ingenic/jz4780.dtsi = b/arch/mips/boot/dts/ingenic/jz4780.dtsi >> index 5f44cf004d473..b5299eaffb84a 100644 >> --- a/arch/mips/boot/dts/ingenic/jz4780.dtsi >> +++ b/arch/mips/boot/dts/ingenic/jz4780.dtsi >> @@ -155,7 +155,7 @@ rtc_dev: rtc@10003000 { >> clock-names =3D "rtc"; >> }; >>=20 >> - pinctrl: pin-controller@10010000 { >> + pinctrl: pinctrl@10010000 { >=20 > Do it once for all DTSes, not one file at a time. There are four more > places with this. Well, automation has no notion of "similarity" in this case to merge several patches. And they are not related. Every one is based on a different .yaml schema file. That in all cases the result looks similar comes from similar requirements by the schemata and has no inherent connection.