[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y6dsWVspi9tGNid5@kbusch-mbp.dhcp.thefacebook.com>
Date: Sat, 24 Dec 2022 14:17:13 -0700
From: Keith Busch <kbusch@...nel.org>
To: Pali Rohár <pali@...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 Sat, Dec 24, 2022 at 05:36:02PM +0100, Pali Rohár wrote:
> On Saturday 24 December 2022 17:18:51 Borislav Petkov wrote:
> >
> > So you don't have to get all worked up about it - if it is really used,
> > I'm sure the maintainers involved will do the right decision. The point
> > is, finding out whether something still has users and with the latest
> > kernel is not always trivial.
>
> I agree that finding out such information is hard. But do not take me
> wrong, but if people are lazy and do not look into in-tree kernel
> documentation and check it, then I'm loosing motivation to keep in-tree
> kernel documentation up-to-date...
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?
Powered by blists - more mailing lists