linux-kernel - Re: [PATCH v2 2/2] reset: always include 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMRc=MeOsUOJTx1-UVdQQzxk=KWyOoO7NwfAhrNDJmUv7kOScw@mail.gmail.com>
Date: Thu, 23 Oct 2025 14:04:53 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>
Cc: Philipp Zabel <p.zabel@...gutronix.de>, Geert Uytterhoeven <geert@...ux-m68k.org>, 
	linux-renesas-soc@...r.kernel.org, 
	Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>, 
	Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] reset: always include RESET_GPIO driver if possible

On Thu, Oct 23, 2025 at 1:18 PM Wolfram Sang
<wsa+renesas@...g-engineering.com> wrote:
>
> > > I see. That kind of spoils my assumption that it is a fallback supported
> > > by the core. Darn, I would still like to have it, but it seems more
> > > complicated than I have time for it :(
> > >
> >
> > As soon as my two other reset series land in next, I will finish my
> > work on converting the reset core to fwnode which should help.
>
> Cool! Then you bring back my argument, that it should be always compiled
> in because it is a core feature ;)
>

No, I still think it should be a module by default with an option to
build it in if the platform demands it. Just like 95% of the drivers
out there.

Bartosz