netdev - Re: [PATCH v3] MAINTAINERS: Add new maintainers to Redpine driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <dd9a86af-e41a-3450-5e52-6473561a3e18@denx.de>
Date: Mon, 5 Jun 2023 11:59:41 +0200
From: Marek Vasut <marex@...x.de>
To: Jérôme Pouiller <jerome.pouiller@...abs.com>,
 Kalle Valo <kvalo@...nel.org>,
 Ganapathi Kondraju <ganapathi.kondraju@...abs.com>
Cc: linux-wireless@...r.kernel.org, Amitkumar Karwar <amitkarwar@...il.com>,
 Amol Hanwate <amol.hanwate@...abs.com>, Angus Ainslie <angus@...ea.ca>,
 Jakub Kicinski <kuba@...nel.org>, Johannes Berg <johannes@...solutions.net>,
 Martin Fuzzey <martin.fuzzey@...wbird.group>,
 Martin Kepplinger <martink@...teo.de>,
 Narasimha Anumolu <narasimha.anumolu@...abs.com>,
 Sebastian Krzyszkowiak <sebastian.krzyszkowiak@...i.sm>,
 Shivanadam Gude <shivanadam.gude@...abs.com>,
 Siva Rebbagondla <siva8118@...il.com>,
 Srinivas Chappidi <srinivas.chappidi@...abs.com>, netdev@...r.kernel.org
Subject: Re: [PATCH v3] MAINTAINERS: Add new maintainers to Redpine driver

On 6/1/23 12:47, Jérôme Pouiller wrote:
> On Saturday 27 May 2023 23:12:16 CEST Marek Vasut wrote:
>> On 2/27/23 11:28, Kalle Valo wrote:
>>> Ganapathi Kondraju <ganapathi.kondraju@...abs.com> writes:
>>>
>>>> Silicon Labs acquired Redpine Signals recently. It needs to continue
>>>> giving support to the existing REDPINE WIRELESS DRIVER. This patch adds
>>>> new Maintainers for it.
>>>>
>>>> Signed-off-by: Ganapathi Kondraju <ganapathi.kondraju@...abs.com>
>>>> ---
>>>> V2:
>>>> - Add proper prefix for patch subject.
>>>> - Reorder the maintainers list alphabetically.
>>>> - Add a new member to the list.
>>>> ---
>>>> V3:
>>>> - Fix sentence formation in the patch subject and description.
>>>> ---
>>>>
>>>>    MAINTAINERS | 8 +++++++-
>>>>    1 file changed, 7 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>>> index ea941dc..04a08c7 100644
>>>> --- a/MAINTAINERS
>>>> +++ b/MAINTAINERS
>>>> @@ -17709,8 +17709,14 @@ S:  Maintained
>>>>    F: drivers/net/wireless/realtek/rtw89/
>>>>
>>>>    REDPINE WIRELESS DRIVER
>>>> +M:  Amol Hanwate <amol.hanwate@...abs.com>
>>>> +M:  Ganapathi Kondraju <ganapathi.kondraju@...abs.com>
>>>> +M:  Jérôme Pouiller <jerome.pouiller@...abs.com>
>>>> +M:  Narasimha Anumolu <narasimha.anumolu@...abs.com>
>>>> +M:  Shivanadam Gude <shivanadam.gude@...abs.com>
>>>> +M:  Srinivas Chappidi <srinivas.chappidi@...abs.com>
>>>>    L: linux-wireless@...r.kernel.org
>>>> -S:  Orphan
>>>> +S:  Maintained
>>>>    F: drivers/net/wireless/rsi/
>>>
>>> For me six maintainers is way too much. Just last November I marked this
>>> driver as orphan, I really do not want to add all these people to
>>> MAINTAINERS and never hear from them again.
>>>
>>> Ideally I would prefer to have one or two maintainers who would be
>>> actively working with the drivers. And also I would like to see some
>>> proof (read: reviewing patches and providing feedback) that the
>>> maintainers are really parciticiping in upstream before changing the
>>> status.
>>
>> Has there been any progress on improving this driver maintainership
>> since this patch ?
> 
> Hello Marek,
> 
> The situation is still blurry. There is a willing to maintain this driver
> (and several people would like I take care of that). However, the effort
> to properly support this driver is still unknown (in fact, I have not yet
> started to really look at the situation).

I have to admit, the aforementioned paragraph is quite disturbing, 
considering that this patch adds 6 maintainers, is already in V3, and so 
far it is not even clear to silabs how much effort it would be to 
maintain driver for their own hardware, worse, silabs didn't even check. 
What is the point of adding those maintainers then ?

> Is this driver blocking some architectural changes? Kalle is talking about
> patches to review. Can you point me on them?

You can look up patches at patchwork.kernel.org or lore.kernel.org and 
search for "rsi:" or "wifi: rsi:" tags.

This driver is basically unusable and I am tempted to send a patch to 
move it to staging and possibly remove it altogether.

WiFi/BT coex is broken, WiFi stability is flaky at best, BT often 
crashes the firmware. There are very iffy design decisions in the driver 
and other weird defects I keep finding.

Multiple people tried to fix at least a couple of basic problems, so the 
driver can be used at all, but there is no documentation and getting 
support regarding anything from RSI is a total waste of time. Sadly, the 
only reference material I could find and work with is some downstream 
goo, which is released in enormous single-commit code dumps with +/- 
thousands of lines of changes and with zero explanation what each change 
means.

> Anyway, I would like to come back with a plan by the end of the summer.

Sure.

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?