[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a3y5WxsibmTzvhv76G+rQ1Zjo_tW0UkXku0VnZdQa-__A@mail.gmail.com>
Date: Sun, 8 Nov 2020 12:42:49 +0100
From: Arnd Bergmann <arnd@...nel.org>
To: Kalle Valo <kvalo@...eaurora.org>
Cc: Jakub Kicinski <kuba@...nel.org>,
Networking <netdev@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-wireless <linux-wireless@...r.kernel.org>,
bridge@...ts.linux-foundation.org, linux-hams@...r.kernel.org,
Christoph Hellwig <hch@....de>,
Alexander Viro <viro@...iv.linux.org.uk>,
Johannes Berg <johannes@...solutions.net>,
Andrew Lunn <andrew@...n.ch>,
Heiner Kallweit <hkallweit1@...il.com>
Subject: Re: [RFC net-next 00/28] ndo_ioctl rework
On Sun, Nov 8, 2020 at 12:21 PM Kalle Valo <kvalo@...eaurora.org> wrote:
> Jakub Kicinski <kuba@...nel.org> writes:
>
> So I don't know what to do. Should we try adding a warning like below? :)
>
> "This ancient driver will be removed from the kernel in 2022, but if
> it still works send report to <...@...> to avoid the removal."
>
> How do other subsystems handle ancient drivers?
A good way to get everyone's attention would be to collect as many
drivers as possible that are almost certainly unused and move them to
drivers/staging/ with a warning like the above, as I just did for
drivers/wimax. That would make it to the usual news outlets
and lead to the remaining users (if any) noticing it so they can then
ask for the drivers to be moved back -- or decide it's time to let go
if the hardware can easily be replaced.
Arnd
Powered by blists - more mailing lists