From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id F27AAC4345F for ; Thu, 25 Apr 2024 16:30:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=s9OfuseTkxqocmi1udE6he3a7WUI2ibja8ouXTXWDZU=; b=KzvEDYxHGixjZX Lg07FnXfF+6urntqAMLtBvilHpT8R/0VcGWaPc6lO6MFBr6XU6oWd8SQgDtaFc3rQHixNTdbg/UL7 9kukca35AVgHyevMCQbjPyLDmwKDo2jJvaIofrtbUqHoTdExqwZmt41+R3TIQe4WZsjvoB6WA7I0p aX421R9LAEfFpEBcgdeK1SmBCXRi2IFStqfpzvbdswfztg1UnwcgpvZLsvL5ZyaA6OZA/tEWj/ks1 aoKdc9WyKvHWEdgPLhSxqtlloOmMwaM11YfG+cS/N6tRr3dsvIg1qdHDe28opaEqfVlGMQ37gpQcR iiQWUaDixRdrtM7ECgiQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1s01zf-00000009Nle-39WJ; Thu, 25 Apr 2024 16:30:43 +0000 Received: from sin.source.kernel.org ([2604:1380:40e1:4800::1]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1s01zd-00000009Nkg-3EKZ for linux-arm-kernel@lists.infradead.org; Thu, 25 Apr 2024 16:30:43 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id 839E1CE19B1; Thu, 25 Apr 2024 16:30:38 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7FFADC113CC; Thu, 25 Apr 2024 16:30:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1714062637; bh=o6qnkohJ43I0c9dUSdw3e1QtuR0Qmn9fqg4+khVlmGU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=jHCB1LyzEL+j8iFGW5mQoqMy1mB1Uv50bhBymZOdc1h+qVy3ZCZe/494SBd2S1fj/ OHbyMfU6/0D9dOG4YWHpFE/YcC1ckg+qNP1mvehERsCl4sfzKGv72r1+P3qZB62M70 Jy5LZoZZ2BLzcVor9re17KnYDOVwyfMcUsYKvy9dBuq/yLNCihv5OWGWp8qfN4FiJi WfNS+53EGZrcPHi4G1E5qdqXyJDqcVKETUnmsr3we7x0gBZ8x83FlDqjJkXCiKPSJd dpuDmBiRVV3j53YaKEUYfcWmviAAL1RIV2IhIgpvumhO90gvGitPGCgu1DS7srJJwf g7evSH24HCbAw== Date: Thu, 25 Apr 2024 11:30:35 -0500 From: Rob Herring To: Patrick Delaunay Cc: Alexandre TORGUE , Liam Girdwood , Mark Brown , Krzysztof Kozlowski , Conor Dooley , Maxime Coquelin , Olivier Moysan , Arnaud Pouliquen , Pascal Paillet , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com Subject: Re: [PATCH 0/3] ARM: st: use a correct pwr compatible for stm32mp15 Message-ID: <20240425163035.GA2783061-robh@kernel.org> References: <20240425074835.760134-1-patrick.delaunay@foss.st.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20240425074835.760134-1-patrick.delaunay@foss.st.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240425_093042_045130_7A71F476 X-CRM114-Status: GOOD ( 11.44 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Apr 25, 2024 at 09:48:31AM +0200, Patrick Delaunay wrote: > > This patchset removes the unexpected comma in the PWR compatible > "st,stm32mp1,pwr-reg" and uses a new compatible "st,stm32mp1-pwr-reg" > in STM3MP15 device trees. Why? I don't see any warnings from this. Yes, we wouldn't new cases following this pattern, but I don't think it is worth maintaining support for both strings. We're stuck with it. And the only way to maintain forward compatibility is: compatible = "st,stm32mp1-pwr-reg", "st,stm32mp1,pwr-reg"; Rob _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel