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 E2352C4829A for ; Tue, 13 Feb 2024 16:19:20 +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=Q7J2JSXeejDdJhkTWS3fYxNGBWUxLntEAJyXqlmqmgs=; b=fq1jN7z5pEdwAh +kY2rPktDMapu8z/TVsJZnKztur9UsfZXFcks1ABUlWxBBDxw8JS3JKR5yeDP4nQsOnbwdjESog7J v1D6snTK3E5k4M2AzHg2dKQ9vJ66lTkEpQd9BDrfTArNNR/a4xoim2QuzfdNMFa3glUMwKLID++Og DyjBrrfcxTln7DsFAZo3t5ljoX3eE/ZWG2Bp2tZly+VPhHbXO9jGCe5TSwU6MWicmNgIXKBvoBEV0 WTZnYFGkZtGnKBVd1m0X7UGC4ISZwvcJb/A7XN5nDi+PQ4TcGi6cWULxW9+lJ5Csec+wkoobr5FZ5 3r7nFDQubHgd46ZrOIlQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1rZvV0-00000009vPd-3J98; Tue, 13 Feb 2024 16:19:10 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1rZvUy-00000009vOu-0xcN for linux-arm-kernel@lists.infradead.org; Tue, 13 Feb 2024 16:19:09 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id A277B6156E; Tue, 13 Feb 2024 16:19:07 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2F88FC433F1; Tue, 13 Feb 2024 16:19:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1707841147; bh=kH3SOr9TCZKMlM/gQHV4yrLVT8Tx3VF0/Q1Pp1UtomY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=awGYDM7EJhxCo8En97K9nMJomm/Ni4hAS/m42KS9QsV5x0PylA5YYTvIdDnxl+ROs mYSU+OkdrzNM4SuQN3/USCGlKZXVxjWY/DVj57ZwSt5wSx+aiLo6qaLjz2dRU4lgnj WKUEIU0LsqSQnYkvyoUKG2OnvJqGJAOJeBbIe9e7wVQedCBW9J6JB4F6w3qJvJa+tb 0gqIsMqA4Pr4aj+ArALEOuhjf2HrGsE1Bk1EaMZDweNOGD2fLnLPgtnd6SoZyNzfOf nalnmi2X7mdUwHuHg65QnnIgh0Hc7MUqkiv1zG/bV7r2z8oAMMhwFmNrOCt14eJnfk KJgmdZpoUFVig== Date: Tue, 13 Feb 2024 10:19:05 -0600 From: Rob Herring To: Krzysztof Kozlowski Cc: Andy Shevchenko , Ralf Schlatterbeck , Geert Uytterhoeven , Linus Walleij , Miguel Ojeda , Krzysztof Kozlowski , Conor Dooley , Robin van der Gracht , Paul Burton , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/3] dt-bindings: auxdisplay: hit, hd44780: drop redundant GPIO node Message-ID: <20240213161905.GA1459669-robh@kernel.org> References: <20240212083426.26757-1-krzysztof.kozlowski@linaro.org> <2922eece-5486-4eff-af99-f7060cb61d17@linaro.org> <20240212115837.efz73yxinkysdmgh@runtux.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240213_081908_331719_B48B0672 X-CRM114-Status: GOOD ( 12.95 ) 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 Mon, Feb 12, 2024 at 02:59:02PM +0100, Krzysztof Kozlowski wrote: > On 12/02/2024 14:43, Andy Shevchenko wrote: > > On Mon, Feb 12, 2024 at 02:38:27PM +0100, Krzysztof Kozlowski wrote: > >> On 12/02/2024 12:58, Ralf Schlatterbeck wrote: > > > > ... > > > >> Anyway, binding examples should not be collection of unrelated > >> solutions, because then we should accept for each device schema several > >> other variations and combinations. > > > > Is this documented? > > Yes, writing schema says what the example is. We repeated it multiple > times on multiple reviews, we made multiple commits multiple times and I > briefly mentioned it also in my talks. While yes, this is the guidance, I think this case has provided enough justification to keep it. Let's move on please. Rob _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel