linux-kernel - Re: [PATCH v2 1/2] reset: always bail out on missing RESET

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]

Message-ID: <9ba9f4b1-5bdf-4242-aba9-8035571caa1c@linaro.org>
Date: Mon, 3 Nov 2025 15:53:58 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Philipp Zabel <p.zabel@...gutronix.de>,
 Wolfram Sang <wsa+renesas@...g-engineering.com>,
 linux-renesas-soc@...r.kernel.org
Cc: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/2] reset: always bail out on missing RESET_GPIO
 driver

On 30/10/2025 13:54, Philipp Zabel wrote:
> On Mi, 2025-10-15 at 22:59 +0200, Wolfram Sang wrote:
>> Optional GPIOs mean they can be omitted. If they are described, a
>> failure in acquiring them still needs to be reported. When the
>> RESET_GPIO is not enabled (so the reset core cannot provide its assumed
>> fallback), the user should be informed about it. So, not only bail out
>> but also give a hint how to fix the situation. This means the check has
>> to be moved after ensuring the GPIO is really described.
>>
>> Signed-off-by: Wolfram Sang <wsa+renesas@...g-engineering.com>
> 
> Patch 1 applied to reset/next, thanks!
> 
> [1/2] reset: always bail out on missing RESET_GPIO driver
>       https://git.pengutronix.de/cgit/pza/linux/commit/?id=25d4d4604d01


Why? This wasn't tested and wasn't reviewed... there were objections to
this patchset and long discussion.

Best regards,
Krzysztof