Received-SPF: pass (google.com: domain of linux-kernel+bounces-211539-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
Date: Wed, 12 Jun 2024 14:11:57 +0100
From: Sudeep Holla <sudeep.holla@arm.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Rob Herring <robh@kernel.org>, Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Liviu Dudau <liviu.dudau@arm.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH 1/2] dt-bindings: arm: arm,juno-fpga-apb-regs: document
 FPGA syscon
Message-ID: <ZmmenchJPyxrbIXi@bogus>
References: <20240518203903.119608-1-krzysztof.kozlowski@linaro.org>
 <171741897752.2195655.18414699008765504203.b4-ty@arm.com>
 <47ddbc43-889a-4def-8e39-e4f166eae667@linaro.org>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <47ddbc43-889a-4def-8e39-e4f166eae667@linaro.org>

On Wed, Jun 12, 2024 at 11:13:32AM +0200, Krzysztof Kozlowski wrote:
> On 03/06/2024 14:51, Sudeep Holla wrote:
> > On Sat, 18 May 2024 22:39:02 +0200, Krzysztof Kozlowski wrote:
> >> Add dedicated bindings for the FPGA syscon registers on ARM Juno board,
> >> to fully document the block and also fix dtbs_check warning:
> >>
> >>   juno.dtb: apbregs@10000: compatible: ['syscon', 'simple-mfd'] is too short
> >
> > Applied to sudeep.holla/linux (for-next/vexpress/updates), thanks!
> >
> > [1/2] dt-bindings: arm: arm,juno-fpga-apb-regs: document FPGA syscon
> >       https://git.kernel.org/sudeep.holla/c/3e295d8b4731
> > [2/2] arm64: dts: juno: add dedicated FPGA syscon compatible
> >       https://git.kernel.org/sudeep.holla/c/2e84e7ed7b02
>
> Thanks. It seems your tree is not in the linux-next or this branch is
> not in next, because these patches are not available in next after a
> week. Maybe you need to update the branches being fed to next (including
> pending-fixes etc.).
>

Done now. It is just that I missed to push the updates to my for-linux-next.
I got it ready when I responded to this thread and forgot to push. I didn't
queue anything after that and completely lost track ????.

--
Regards,
Sudeep