[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221224213646.zyosaq7hnlsaje4b@pali>
Date: Sat, 24 Dec 2022 22:36:46 +0100
From: Pali Rohár <pali@...nel.org>
To: Keith Busch <kbusch@...nel.org>
Cc: Borislav Petkov <bp@...en8.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jens Axboe <axboe@...nel.dk>, linux-kernel@...r.kernel.org,
Christoph Hellwig <hch@...radead.org>,
Thomas Maier <balagi@...tmail.de>, linux-block@...r.kernel.org
Subject: Re: [PATCH] pktcdvd: remove driver.
On Saturday 24 December 2022 14:17:13 Keith Busch wrote:
> As a matter of procedure, could patches deprecating modules perhaps add
> a loud kernel warning message somewhere in the module's execution path
> as a means to mitigate any surprises for people using it?
Sounds like a good idea. But it is needed to find a place for "somewhere".
And message should contain what does that deprecation means. Because for
more software products it means that software is being replaced by
another one. So it could be confusing that it is just needed to switch
from module A to module B and that is all. But for this case there is no
replacement.
And based on my experience, users (including me) are using distributions
LTS kernels in production. So do not forget that it takes lot of time
until some distributions switch from one LTS version to another LTS
version and so it would take lot of time until deprecation warning is
visible to user. (Maybe deprecation information could be "backported" to
LTS kernels?)
In any case I would prefer some documented webpage with all deprecation
information. Like there is releases webpage which says exact day when
particular LTS version is EOL: https://kernel.org/category/releases.html
Powered by blists - more mailing lists