linux-kernel - Re: [PATCH RESEND v5 0/2] regulator: sun20i: Add Allwinner D1 LDOs driver

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] [thread-next>] [day] [month] [year] [list]

Date: Tue, 7 May 2024 23:16:50 +0800
From: Chen-Yu Tsai <wens@...nel.org>
To: Mark Brown <broonie@...nel.org>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, 
	Conor Dooley <conor+dt@...nel.org>, Jernej Skrabec <jernej.skrabec@...il.com>, 
	Samuel Holland <samuel@...lland.org>, linux-kernel@...r.kernel.org, 
	devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, 
	linux-sunxi@...ts.linux.dev
Subject: Re: [PATCH RESEND v5 0/2] regulator: sun20i: Add Allwinner D1 LDOs driver

On Tue, May 7, 2024 at 10:46 PM Mark Brown <broonie@...nel.org> wrote:
>
> On Tue, May 07, 2024 at 12:13:41PM +0800, Chen-Yu Tsai wrote:
>
> > This is a resend of the Allwinner D1 LDO driver series, separated by
> > subsystem. This part contains just the regulator driver bits. The sunxi
> > SRAM binding part will be sent out after the merge window due to a
> > conflict in next.
>
> ...
>
> > A binding and driver change is required for the SRAM controller, to
> > accept the regulators device as its child node.
>
> This says that the driver depends on the SRAM change which isn't getting
> merged this time round?

The SRAM driver change was already merged. The regulator DT binding doesn't
depend on the SRAM binding change; it's the other way around: the SRAM
binding change adds a reference to the new regulator binding.

Hope that explains things.

ChenYu