public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Keith Busch <kbusch@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jens Axboe <axboe@kernel.dk>,
	linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	Thomas Maier <balagi@justmail.de>,
	linux-block@vger.kernel.org
Subject: Re: [PATCH] pktcdvd: remove driver.
Date: Sat, 24 Dec 2022 22:36:46 +0100	[thread overview]
Message-ID: <20221224213646.zyosaq7hnlsaje4b@pali> (raw)
In-Reply-To: <Y6dsWVspi9tGNid5@kbusch-mbp.dhcp.thefacebook.com>

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

  reply	other threads:[~2022-12-24 21:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 18:27 [PATCH] pktcdvd: remove driver Greg Kroah-Hartman
2022-12-02 19:35 ` Jens Axboe
2022-12-03 14:08   ` Greg Kroah-Hartman
     [not found] ` <20221224095353.w32xhmyzlft6qi4v@pali>
2022-12-24 10:03   ` Greg Kroah-Hartman
2022-12-24 10:11     ` Pali Rohár
2022-12-24 12:24       ` Greg Kroah-Hartman
2022-12-24 13:34         ` Pali Rohár
2022-12-24 15:14           ` Borislav Petkov
2022-12-24 15:48             ` Pali Rohár
2022-12-24 15:58               ` Borislav Petkov
2022-12-24 16:00                 ` Pali Rohár
2022-12-24 16:18                   ` Borislav Petkov
2022-12-24 16:36                     ` Pali Rohár
2022-12-24 21:17                       ` Keith Busch
2022-12-24 21:36                         ` Pali Rohár [this message]
2022-12-24 21:46                           ` Slade Watkins
2022-12-24 16:24             ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221224213646.zyosaq7hnlsaje4b@pali \
    --to=pali@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=balagi@justmail.de \
    --cc=bp@alien8.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=kbusch@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox