All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Arnd Bergmann <arnd@kernel.org>,  Arnd Bergmann <arnd@arndb.de>,
	Nicolas Ferre <nicolas.ferre@microchip.com>,
	 Alexandre Belloni <alexandre.belloni@bootlin.com>,
	 Claudiu Beznea <claudiu.beznea@tuxon.dev>,
	 Jakub Kicinski <kuba@kernel.org>,  Pavel Machek <pavel@ucw.cz>,
	 "David S. Miller" <davem@davemloft.net>,
	 Larry Finger <Larry.Finger@lwfinger.net>,
	 linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	 linux-arm-kernel@lists.infradead.org,
	linux-staging@lists.linux.dev
Subject: Re: [PATCH] [RFC] wireless: move obsolete drivers to staging
Date: Wed, 11 Oct 2023 10:29:58 +0300	[thread overview]
Message-ID: <87r0m1fwg9.fsf@kernel.org> (raw)
In-Reply-To: <2023101139-pyromania-game-2237@gregkh> (Greg Kroah-Hartman's message of "Wed, 11 Oct 2023 08:16:38 +0200")

Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:

> On Wed, Oct 11, 2023 at 08:40:00AM +0300, Kalle Valo wrote:
>
>> We (the wireless folks) have been talking about dropping legacy drivers
>> on and off for several years now. The problem is that we don't know
>> which of them work and which not, for example IIRC someone reported
>> recently that wl3501 still works.
>> 
>> Personally I would be extremly happy to remove all the ancient drivers
>> as that reduces the amount of code for us to maintain but is that the
>> right thing to do for the users? I don't have an answer to that,
>> comments very welcome.
>> 
>> I have been also wondering if I should add warnings like this to every
>> ancient driver to see if there are any users left:
>> 
>> "wl3501 wireless driver will be removed in 2024. If the driver still
>> works and you are using it send a report NOW to
>> linux-wireless@vger.kernel.org to avoid the removal."
>> 
>> But with the long release cycles the kernel and distros have I doubt
>> waiting for a year is enough, it should be more like three years.
>
> No matter what the time frame is, it's never going to line up with all
> distros, or catch everyone properly.

Yeah, that's true.

> I recommend, just delete all the ones you feel are not being used, in a
> patch that removes them one-by-one, so that it is trivial to revert if
> someone shows up and says "hey, my device stopped working!" a few years
> in the future.

I'm starting to lean towards this as well. We have talked about this for
so long now but no practical solution ever found so maybe just bite the
bullet finally. What do others think?

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Arnd Bergmann <arnd@kernel.org>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
	linux-wireless@vger.kernel.org,
	Claudiu Beznea <claudiu.beznea@tuxon.dev>,
	Pavel Machek <pavel@ucw.cz>, Jakub Kicinski <kuba@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	linux-arm-kernel@lists.infradead.org,
	Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [PATCH] [RFC] wireless: move obsolete drivers to staging
Date: Wed, 11 Oct 2023 10:29:58 +0300	[thread overview]
Message-ID: <87r0m1fwg9.fsf@kernel.org> (raw)
In-Reply-To: <2023101139-pyromania-game-2237@gregkh> (Greg Kroah-Hartman's message of "Wed, 11 Oct 2023 08:16:38 +0200")

Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:

> On Wed, Oct 11, 2023 at 08:40:00AM +0300, Kalle Valo wrote:
>
>> We (the wireless folks) have been talking about dropping legacy drivers
>> on and off for several years now. The problem is that we don't know
>> which of them work and which not, for example IIRC someone reported
>> recently that wl3501 still works.
>> 
>> Personally I would be extremly happy to remove all the ancient drivers
>> as that reduces the amount of code for us to maintain but is that the
>> right thing to do for the users? I don't have an answer to that,
>> comments very welcome.
>> 
>> I have been also wondering if I should add warnings like this to every
>> ancient driver to see if there are any users left:
>> 
>> "wl3501 wireless driver will be removed in 2024. If the driver still
>> works and you are using it send a report NOW to
>> linux-wireless@vger.kernel.org to avoid the removal."
>> 
>> But with the long release cycles the kernel and distros have I doubt
>> waiting for a year is enough, it should be more like three years.
>
> No matter what the time frame is, it's never going to line up with all
> distros, or catch everyone properly.

Yeah, that's true.

> I recommend, just delete all the ones you feel are not being used, in a
> patch that removes them one-by-one, so that it is trivial to revert if
> someone shows up and says "hey, my device stopped working!" a few years
> in the future.

I'm starting to lean towards this as well. We have talked about this for
so long now but no practical solution ever found so maybe just bite the
bullet finally. What do others think?

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-10-11  7:27 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10 15:27 [PATCH] [RFC] wireless: move obsolete drivers to staging Arnd Bergmann
2023-10-10 15:27 ` Arnd Bergmann
2023-10-10 16:08 ` Greg Kroah-Hartman
2023-10-10 16:08   ` Greg Kroah-Hartman
2023-10-11  5:40   ` Kalle Valo
2023-10-11  5:40     ` Kalle Valo
2023-10-11  6:16     ` Greg Kroah-Hartman
2023-10-11  6:16       ` Greg Kroah-Hartman
2023-10-11  7:29       ` Kalle Valo [this message]
2023-10-11  7:29         ` Kalle Valo
2023-10-11 15:09         ` Jakub Kicinski
2023-10-11 15:09           ` Jakub Kicinski
2023-10-12 11:47           ` Kalle Valo
2023-10-12 11:47             ` Kalle Valo
2023-10-12 14:36             ` Arnd Bergmann
2023-10-12 14:36               ` Arnd Bergmann
2023-10-12 14:48               ` Kalle Valo
2023-10-12 14:48                 ` Kalle Valo
2023-10-12 15:11                 ` Geert Uytterhoeven
2023-10-12 15:11                   ` Geert Uytterhoeven
2023-10-12 15:11                   ` Geert Uytterhoeven
2023-10-12 15:28               ` Johannes Berg
2023-10-12 15:28                 ` Johannes Berg
2023-10-12 15:28                 ` Johannes Berg
2023-10-12 15:39                 ` Geert Uytterhoeven
2023-10-12 15:39                   ` Geert Uytterhoeven
2023-10-12 15:39                   ` Geert Uytterhoeven
2023-10-12 15:41                   ` Johannes Berg
2023-10-12 15:41                     ` Johannes Berg
2023-10-12 15:41                     ` Johannes Berg
2023-10-12 16:36                     ` Geoff Levand
2023-10-12 16:36                       ` Geoff Levand
2023-10-12 16:36                       ` Geoff Levand
2023-10-13 15:44                       ` Arnd Bergmann
2023-10-13 15:44                         ` Arnd Bergmann
2023-10-13 15:44                         ` Arnd Bergmann
2023-10-13 18:02                         ` Johannes Berg
2023-10-13 18:02                           ` Johannes Berg
2023-10-13 18:02                           ` Johannes Berg
2023-10-18 20:37                           ` Jeff Johnson
2023-10-18 20:37                             ` Jeff Johnson
2023-10-18 20:37                             ` Jeff Johnson
2023-10-12 16:16               ` Philipp Hortmann
2023-10-12 16:16                 ` Philipp Hortmann
2023-10-12 16:18               ` Dan Williams
2023-10-12 16:18                 ` Dan Williams
2023-10-11  7:24     ` Arnd Bergmann
2023-10-11  7:24       ` Arnd Bergmann
2023-10-11  7:41       ` Greg Kroah-Hartman
2023-10-11  7:41         ` Greg Kroah-Hartman
2023-10-11  8:44       ` Kalle Valo
2023-10-11  8:44         ` Kalle Valo
2023-10-11  9:01         ` Arnd Bergmann
2023-10-11  9:01           ` Arnd Bergmann
2023-10-11 18:13 ` Philipp Hortmann
2023-10-11 18:13   ` Philipp Hortmann
2023-10-11 20:22   ` Arnd Bergmann
2023-10-11 20:22     ` Arnd Bergmann
2023-10-12  6:23     ` Dan Carpenter
2023-10-12  6:23       ` Dan Carpenter
2023-10-13  6:42 ` Philipp Hortmann
2023-10-13  6:42   ` Philipp Hortmann
2023-10-13 15:36   ` Arnd Bergmann
2023-10-13 15:36     ` Arnd Bergmann
2023-10-13 16:24     ` Larry Finger
2023-10-13 16:24       ` Larry Finger
2023-10-15 18:42     ` Philipp Hortmann
2023-10-15 18:42       ` Philipp Hortmann
2023-10-18 16:05       ` Arnd Bergmann
2023-10-18 16:05         ` Arnd Bergmann
2023-10-13 11:43 ` kernel test robot

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=87r0m1fwg9.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=alexandre.belloni@bootlin.com \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=pavel@ucw.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.