From: Angus Ainslie <angus@akkea.ca>
To: "Jérôme Pouiller" <jerome.pouiller@silabs.com>
Cc: Kalle Valo <kvalo@kernel.org>,
Ganapathi Kondraju <ganapathi.kondraju@silabs.com>,
Marek Vasut <marex@denx.de>,
linux-wireless@vger.kernel.org,
Amitkumar Karwar <amitkarwar@gmail.com>,
Amol Hanwate <amol.hanwate@silabs.com>,
Jakub Kicinski <kuba@kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
Martin Fuzzey <martin.fuzzey@flowbird.group>,
Martin Kepplinger <martink@posteo.de>,
Narasimha Anumolu <narasimha.anumolu@silabs.com>,
Sebastian Krzyszkowiak <sebastian.krzyszkowiak@puri.sm>,
Shivanadam Gude <shivanadam.gude@silabs.com>,
Siva Rebbagondla <siva8118@gmail.com>,
Srinivas Chappidi <srinivas.chappidi@silabs.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH v3] MAINTAINERS: Add new maintainers to Redpine driver
Date: Fri, 09 Jun 2023 08:46:28 -0700 [thread overview]
Message-ID: <50ab38c7104b99277bca512ba8f59255@akkea.ca> (raw)
In-Reply-To: <3166282.5fSG56mABF@pc-42>
Hi Jérôme,
On 2023-06-09 08:10, Jérôme Pouiller wrote:
>
> You are talking about this driver[1] I assume?
>
> [1]: https://github.com/SiliconLabs/RS911X-nLink-OSD
>
> [...]
>> In the meantime, since RSI neglected this driver for years, what would
>> be the suggestion for people who are stuck with the RSI WiFi hardware?
>
> Unfortunately, my only suggestion is to use the downstream driver we
> mentioned above.
That driver isn't really a solution as it rarely applies cleanly to
recent kernels.
The lack of proper commit messages also makes the changes opaque.
Cheers
Angus
next prev parent reply other threads:[~2023-06-09 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 14:08 [PATCH v3] MAINTAINERS: Add new maintainers to Redpine driver Ganapathi Kondraju
2023-02-27 10:28 ` Kalle Valo
2023-05-27 21:12 ` Marek Vasut
2023-06-01 10:47 ` Jérôme Pouiller
2023-06-05 9:59 ` Marek Vasut
2023-06-05 12:00 ` Fuzzey, Martin
2023-06-09 15:10 ` Jérôme Pouiller
2023-06-09 15:46 ` Angus Ainslie [this message]
2023-06-10 12:32 ` Marek Vasut
2023-06-10 12:34 ` Marek Vasut
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=50ab38c7104b99277bca512ba8f59255@akkea.ca \
--to=angus@akkea.ca \
--cc=amitkarwar@gmail.com \
--cc=amol.hanwate@silabs.com \
--cc=ganapathi.kondraju@silabs.com \
--cc=jerome.pouiller@silabs.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marex@denx.de \
--cc=martin.fuzzey@flowbird.group \
--cc=martink@posteo.de \
--cc=narasimha.anumolu@silabs.com \
--cc=netdev@vger.kernel.org \
--cc=sebastian.krzyszkowiak@puri.sm \
--cc=shivanadam.gude@silabs.com \
--cc=siva8118@gmail.com \
--cc=srinivas.chappidi@silabs.com \
/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).