linux-kernel - Re: [PATCH v2 0/2] reset: handle RESET_GPIO better to provide the fallback

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: <61c8e3fc-af35-432f-9bb9-300c953819e4@linaro.org>
Date: Mon, 3 Nov 2025 16:08:42 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
 Wolfram Sang <wsa+renesas@...g-engineering.com>
Cc: linux-renesas-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
 Philipp Zabel <p.zabel@...gutronix.de>
Subject: Re: [PATCH v2 0/2] reset: handle RESET_GPIO better to provide the
 fallback

On 16/10/2025 02:02, Kuninori Morimoto wrote:
> 
> Hi Wolfram
> 
>> After the discussion[1] (Thanks, Philipp!), here is the updated series.
>> Details are in the commit messages. Please let me know what you think.
> 
> Thank you for your help !!
> My board started works again (without .config manual update !)
> 
> Tested-by: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>

Started to work? So was it broken? By what?

This driver was always OPTIONAL, was never meant to be required and
there was no code which was converted to usage of this driver.

I have doubts how this was tested - what exactly problem is being here
solved (except breaking all possible platforms by making this
non-bisectable...).

Best regards,
Krzysztof