linux-kernel - Re: [PATCH 1/2] dt-bindings: arm: arm,juno-fpga-apb-regs: document FPGA syscon

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <ZmmenchJPyxrbIXi@bogus>
Date: Wed, 12 Jun 2024 14:11:57 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>,
	Liviu Dudau <liviu.dudau@....com>,
	Sudeep Holla <sudeep.holla@....com>,
	Lorenzo Pieralisi <lpieralisi@...nel.org>,
	Linus Walleij <linus.walleij@...aro.org>,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org,
	Jiaxun Yang <jiaxun.yang@...goat.com>
Subject: Re: [PATCH 1/2] dt-bindings: arm: arm,juno-fpga-apb-regs: document
 FPGA syscon

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@...00: 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