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: <aQjPstQanpn5zUnf@shikoro>
Date: Mon, 3 Nov 2025 16:52:18 +0100
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: linux-renesas-soc@...r.kernel.org,
	Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
	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


> > What is the benefit of having reset-gpios handling in the reset core
> > optionally and required as a fallback?
> 
> Stable ABI rules require that, it is not about "benefits". Please send
> email to Linus and ask him: "can I make a change which breaks users of ABI".

I don't get it. If a driver already depends on RESET, then only the
handling code is moved from the driver to the reset core. Where is an
ABI breakage there?

> See four reports from Marek Szyprowski.

I am talking about the original i2c-mux patch here. Not the failed
attempt to get it working.


Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ