| 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
| ||
|
Message-ID: <51f28d92-f670-47de-8e2d-53cbecfac081@gmail.com> Date: Sat, 24 Aug 2024 11:08:30 +0200 From: Kryštof Černý <cleverline1mc@...il.com> To: Krzysztof Kozlowski <krzk@...nel.org>, Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, Chen-Yu Tsai <wens@...e.org>, Jernej Skrabec <jernej.skrabec@...il.com>, Samuel Holland <samuel@...lland.org> Cc: devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-sunxi@...ts.linux.dev, linux-kernel@...r.kernel.org Subject: Re: [PATCH PATCH] arm64: dts: sunxi: nanopi-neo-plus2: Add pio regulators I am sorry if the message is wrong, this is my first patch ever sent to the Linux kernel. I have checked the schematic of the board and it shares the same power line with mmc0, so I assumed I can use the same regulator. Thanks for your feedback and I would be glad for your further response. Dne 24. 08. 24 v 9:40 Krzysztof Kozlowski napsal(a): > On 24/08/2024 09:09, Kryštof Černý wrote: >> The board does not have a dedicated regulator for pio and r_pio, >> but this fixes the kernel warning about dummy regulators being used. >> Tested on the actual board. >> > Judging by commit msg these are not correct regulators. Please do not > add incorrect hardware description to silence some warnings coming from > OS. Either you need proper (correct) hardware description or fix the > problem other way, assuming there is anything to fix in the first place. > > Best regards, > Krzysztof >
Powered by blists - more mailing lists