linux-kernel - Re: [PATCH v1 1/1] i2c: core: Propagate all possible errors when requesting recovery GPIOs

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] [day] [month] [year] [list]

Message-ID: <aW6DBSNejuqMU0Kq@smile.fi.intel.com>
Date: Mon, 19 Jan 2026 21:16:21 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>,
	linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 1/1] i2c: core: Propagate all possible errors when
 requesting recovery GPIOs

On Fri, May 02, 2025 at 05:16:48PM +0300, Andy Shevchenko wrote:
> On Wed, Mar 12, 2025 at 04:44:23PM +0200, Andy Shevchenko wrote:
> > On Wed, Feb 12, 2025 at 06:37:01PM +0200, Andy Shevchenko wrote:
> > > If GPIO is available but we can't get it by some other, than deferred probe,
> > > reason, propagate it to the caller.
> > > 
> > > No functional change since i2c_register_adapter() still cares only about
> > > deferred probe.
> > 
> > Any comment on this? It's a month passed without any reaction...
> 
> Yet another ping...

So, can this be applied or should I do something about it?

-- 
With Best Regards,
Andy Shevchenko