[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VfBddSLz47YQkNUOX0PEYzujC2ghFYrhzh+Js5cEoJ_MQ@mail.gmail.com>
Date: Tue, 22 Sep 2020 11:11:02 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: Kent Gibson <warthog618@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH v9 13/20] gpio: uapi: document uAPI v1 as deprecated
On Tue, Sep 22, 2020 at 10:49 AM Arnd Bergmann <arnd@...db.de> wrote:
> On Tue, Sep 22, 2020 at 4:36 AM Kent Gibson <warthog618@...il.com> wrote:
> > /*
> > * ABI v1
> > + *
> > + * This version of the ABI is deprecated and will be removed in the future.
> > + * Use the latest version of the ABI, defined above, instead.
> > */
>
> How intentional is the wording here? It seems unrealistic that the v1 ABI
> would be removed any time soon if there are existing users and applications
> cannot yet rely on v2 to be present in all kernels, so it sounds like a hollow
> threat.
I have similar thoughts when commenting on previous versions of this piece.
> At the same time I can see that telling users it will be removed can lead to
> them moving on to the new version more quickly, so maybe a hollow threat
> is in fact appropriate here ;-)
Users all know that if something will be broken, they may escalate to
Linus T. and get things reverted. So, above depends on the user's
knowledge about the process.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists