linux-kernel - Re: [PATCH 0/2] Name the regulators for QCM6490 Fairphone 5 & SHIFTphone 8

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]

Date: Fri, 21 Jun 2024 01:11:22 -0500
From: Bjorn Andersson <andersson@...nel.org>
To: Konrad Dybcio <konrad.dybcio@...aro.org>,
	Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>,
	Caleb Connolly <caleb@...tmarketos.org>,
	Alexander Martinz <amartinz@...ftphones.com>,
	Luca Weiss <luca.weiss@...rphone.com>
Cc: ~postmarketos/upstreaming@...ts.sr.ht,
	phone-devel@...r.kernel.org,
	linux-arm-msm@...r.kernel.org,
	devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] Name the regulators for QCM6490 Fairphone 5 & SHIFTphone 8


On Tue, 18 Jun 2024 15:30:53 +0200, Luca Weiss wrote:
> As per individual commit messages:
> 
> Without explicitly specifying names for the regulators they are named
> based on the DeviceTree node name. This results in multiple regulators
> with the same name, making debug prints and regulator_summary impossible
> to reason about.
> 
> [...]

Applied, thanks!

[1/2] arm64: dts: qcom: qcm6490-fairphone-fp5: Name the regulators
      commit: 4c3849513fa1b4d9f6fbe08ecd65e2d6ae19c1fb
[2/2] arm64: dts: qcom: qcm6490-shift-otter: Name the regulators
      commit: e160c41b96b6d6f38b8646e3c914c630da21e105

Best regards,
-- 
Bjorn Andersson <andersson@...nel.org>