linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Kalle Valo <kvalo@kernel.org>, Arnd Bergmann <arnd@kernel.org>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	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 09:41:00 +0200	[thread overview]
Message-ID: <2023101115-wackiness-gracious-00a2@gregkh> (raw)
In-Reply-To: <d081871c-977c-43e9-afa3-a3c3e5880fea@app.fastmail.com>

On Wed, Oct 11, 2023 at 09:24:55AM +0200, Arnd Bergmann wrote:
> Debian on the other just enables every driver, so there
> is no good way to know what they actually use.

Yeah, as you point out, we can't go by distro kernel configs as they
obviously error on the side of "build everything!".  But your openwrt
info is good, thanks for that, that's a huge hint that no one uses those
drivers anymore.

greg k-h

_______________________________________________
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:41 UTC|newest]

Thread overview: 31+ 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 16:08 ` Greg Kroah-Hartman
2023-10-11  5:40   ` Kalle Valo
2023-10-11  6:16     ` Greg Kroah-Hartman
2023-10-11  7:29       ` Kalle Valo
2023-10-11 15:09         ` Jakub Kicinski
2023-10-12 11:47           ` Kalle Valo
2023-10-12 14:36             ` Arnd Bergmann
2023-10-12 14:48               ` Kalle Valo
2023-10-12 15:11                 ` Geert Uytterhoeven
2023-10-12 15:28               ` Johannes Berg
2023-10-12 15:39                 ` Geert Uytterhoeven
2023-10-12 15:41                   ` Johannes Berg
2023-10-12 16:36                     ` Geoff Levand
2023-10-13 15:44                       ` Arnd Bergmann
2023-10-13 18:02                         ` Johannes Berg
2023-10-18 20:37                           ` Jeff Johnson
2023-10-12 16:16               ` Philipp Hortmann
2023-10-12 16:18               ` Dan Williams
2023-10-11  7:24     ` Arnd Bergmann
2023-10-11  7:41       ` Greg Kroah-Hartman [this message]
2023-10-11  8:44       ` Kalle Valo
2023-10-11  9:01         ` Arnd Bergmann
2023-10-11 18:13 ` Philipp Hortmann
2023-10-11 20:22   ` Arnd Bergmann
2023-10-12  6:23     ` Dan Carpenter
2023-10-13  6:42 ` Philipp Hortmann
2023-10-13 15:36   ` Arnd Bergmann
2023-10-13 16:24     ` Larry Finger
2023-10-15 18:42     ` Philipp Hortmann
2023-10-18 16:05       ` Arnd Bergmann

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=2023101115-wackiness-gracious-00a2@gregkh \
    --to=gregkh@linuxfoundation.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=kuba@kernel.org \
    --cc=kvalo@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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).