[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240516151958.GA146240@rigel>
Date: Thu, 16 May 2024 23:19:58 +0800
From: Kent Gibson <warthog618@...il.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Vegard Nossum <vegard.nossum@...cle.com>,
Hu Haowen <2023002089@...k.tyut.edu.cn>, linux-gpio@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
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>
Subject: Re: [PATCH v1 1/1] gpio: Remove legacy API documentation
On Thu, May 16, 2024 at 04:54:38PM +0300, Andy Shevchenko wrote:
> 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?
>
I don't know enough about the situation to provide much of an opinion.
I can say that generally speaking I'm not a fan of removing documentation
for an API until the API itself has been completely removed.
And from my experience users will just Google and find the docs from an
old kernel anyway. That point could be used to argue both for and
against - if they can find it anyway there is no harm in removing it.
But probably not much benefit either.
Sorry - that probably doesn't help much.
FWIW you can count me as indifferent.
Cheers,
Kent.
Powered by blists - more mailing lists