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]
Date: Fri, 17 May 2024 02:47:57 -0700
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Linus Walleij <linus.walleij@...aro.org>, Bartosz Golaszewski <brgl@...ev.pl>, 
	Jonathan Corbet <corbet@....net>, Alex Shi <alexs@...nel.org>, Yanteng Si <siyanteng@...ngson.cn>, 
	Vegard Nossum <vegard.nossum@...cle.com>, Kent Gibson <warthog618@...il.com>, 
	Hu Haowen <2023002089@...k.tyut.edu.cn>, linux-gpio@...r.kernel.org, 
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 1/1] gpio: Remove legacy API documentation

On Thu, 16 May 2024 15:54:38 +0200, Andy Shevchenko
<andriy.shevchenko@...ux.intel.com> said:
> On Wed, May 08, 2024 at 01:17:01PM +0300, Andy Shevchenko wrote:
>> In order to discourage people to use old and legacy GPIO APIs
>> remove the respective documentation completely. It also helps
>> further cleanups of the legacy GPIO API leftovers, which is
>> ongoing task.
>
> Bart, Linus, Kent, what do you think about this?
>
> If there is a positive consensus, I would even dare to go for v6.10-rc2
> with it.
>

I don't have a problem with this change but I will not send it before the
v6.11 merge window. Why would I? I'll have it go the normal route, it's not
a fix.

Bart

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ