From: "Arnd Bergmann" <arnd@arndb.de>
To: "Geoff Levand" <geoff@infradead.org>,
"Johannes Berg" <johannes@sipsolutions.net>,
"Geert Uytterhoeven" <geert@linux-m68k.org>
Cc: Arnd Bergmann <arnd@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kalle Valo <kvalo@kernel.org>,
linux-staging@lists.linux.dev, linux-wireless@vger.kernel.org,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
linux-arm-kernel@lists.infradead.org, Pavel Machek <pavel@ucw.cz>,
Jakub Kicinski <kuba@kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
"David S . Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org,
Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [PATCH] [RFC] wireless: move obsolete drivers to staging
Date: Fri, 13 Oct 2023 17:44:43 +0200 [thread overview]
Message-ID: <2fb4f151-9146-4cce-a3e6-ca80a95cf590@app.fastmail.com> (raw)
In-Reply-To: <39719eae-f166-4059-a70d-c6b74ecd46e2@infradead.org>
On Thu, Oct 12, 2023, at 18:36, Geoff Levand wrote:
> On 10/12/23 17:41, Johannes Berg wrote:
>> But seriously - is it worth to try to keep a wireless driver for it if
>> we don't even know anyone using a PS3 at all?
>
> There is still a considerable user base for the PS3, so we
> must keep the ps3-gelic-wireless driver.
Do you know if anyone has tried changing this driver over to the
cfg80211 interface from the wireless extensions? With the
series I have prepared now, it is the only driver outside of
drivers/staging that still uses wext and stops us from removing
that altogether.
[side note: it appears that the PS3 I have is the only model
without wireless networking, as I bought cheapest Asian 20GB version
back in early 2007. It still has the original firmware on it
and should run Linux, but I haven't tried it since at least
2009].
Arnd
next prev parent reply other threads:[~2023-10-13 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231010155444.858483-1-arnd@kernel.org>
[not found] ` <2023101051-unmasked-cleaver-79b3@gregkh>
[not found] ` <87y1g94szz.fsf@kernel.org>
[not found] ` <2023101139-pyromania-game-2237@gregkh>
[not found] ` <87r0m1fwg9.fsf@kernel.org>
[not found] ` <20231011080955.1beeb010@kernel.org>
[not found] ` <87sf6g2hc8.fsf@kernel.org>
[not found] ` <63e57ef8-c9f2-489a-8df8-51dcffd437c6@app.fastmail.com>
[not found] ` <87fs2fgals.fsf@kernel.org>
2023-10-12 15:11 ` [PATCH] [RFC] wireless: move obsolete drivers to staging 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 [this message]
2023-10-13 18:02 ` Johannes Berg
2023-10-18 20:37 ` Jeff Johnson
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=2fb4f151-9146-4cce-a3e6-ca80a95cf590@app.fastmail.com \
--to=arnd@arndb.de \
--cc=Larry.Finger@lwfinger.net \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=geoff@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=johannes@sipsolutions.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=linuxppc-dev@lists.ozlabs.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 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).