Received-SPF: pass (google.com: domain of linux-kernel+bounces-5523-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Tue, 19 Dec 2023 16:55:41 +0100
From: Johan Hovold <johan@kernel.org>
To: Sebastian Reichel <sre@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>, Vinod Koul <vkoul@kernel.org>,
	linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: power: reset: qcom-pon: fix inconsistent
 example
Message-ID: <ZYG88VLLx1nEPOua@hovoldconsulting.com>
References: <20231130173017.12723-1-johan+linaro@kernel.org>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20231130173017.12723-1-johan+linaro@kernel.org>

Hi Sebastian,

On Thu, Nov 30, 2023 at 06:30:17PM +0100, Johan Hovold wrote:
> The current PON example is a bit of a mess after converting the binding
> document to yaml and in the process updating parts of the example to
> match the pmk8350 binding while leaving parts from the older pm8998
> example in place.
> 
> Clean up the example and make it consistent by adding some newline
> separators; dropping labels; removing stray spaces; fixing the PON node
> name; and fixing the unit address so that it matches the interrupt
> specifiers (which re-encodes the PON base address, 0x800 => 0x8).
> 
> Fixes: 76ba1900cb67 ("dt-bindings: power: reset: qcom-pon: Convert qcom PON binding to yaml")
> Signed-off-by: Johan Hovold <johan+linaro@kernel.org>

I noticed that this on is not yet in linux-next so sending a reminder.

Johan