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: <aIDu8McZRsk8xspV@smile.fi.intel.com>
Date: Wed, 23 Jul 2025 17:17:20 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Bartosz Golaszewski <brgl@...ev.pl>
Cc: Arnd Bergmann <arnd@...nel.org>,
	Linus Walleij <linus.walleij@...aro.org>,
	Arnd Bergmann <arnd@...db.de>, Peng Fan <peng.fan@....com>,
	Lee Jones <lee@...nel.org>,
	Koichiro Den <koichiro.den@...onical.com>,
	Geert Uytterhoeven <geert+renesas@...der.be>,
	Alexander Sverdlin <alexander.sverdlin@...il.com>,
	Uwe Kleine-König <ukleinek@...nel.org>,
	linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] gpiolib: make legacy interfaces optional

On Wed, Jul 23, 2025 at 10:39:32AM +0200, Bartosz Golaszewski wrote:
> On Tue, Jul 22, 2025 at 5:36 PM Arnd Bergmann <arnd@...nel.org> wrote:

...

> > +#ifdef CONFIG_GPIOLIB
> > +#include <linux/gpio/consumer.h>
> 
> I want to queue this ASAP but do we really need this guard here?
> consumer.h already guards against !CONFIG_GPIOLIB internally, right?

I probably missed something, but I do not understand why we need this include
at all in the gpio.h.

> > +#endif


-- 
With Best Regards,
Andy Shevchenko



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ