From: Brian Norris <briannorris@chromium.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: Jakub Kicinski <kuba@kernel.org>,
Pink Perfect <pinkperfect2021@gmail.com>,
amitkarwar@gmail.com, ganapathi017@gmail.com,
sharvari.harisangam@nxp.com, huxinming820@gmail.com,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3] wifi: mwifiex: Fix OOB and integer underflow when rx packets
Date: Thu, 20 Jul 2023 10:14:31 -0700 [thread overview]
Message-ID: <ZLlrd4dDz+kA5l18@google.com> (raw)
In-Reply-To: <87sf9j3wd1.fsf@kernel.org>
On Thu, Jul 20, 2023 at 09:55:38AM +0300, Kalle Valo wrote:
> We have four maintainers for mwifiex and total silence:
>
> MARVELL MWIFIEX WIRELESS DRIVER
> M: Amitkumar Karwar <amitkarwar@gmail.com>
> M: Ganapathi Bhat <ganapathi017@gmail.com>
> M: Sharvari Harisangam <sharvari.harisangam@nxp.com>
> M: Xinming Hu <huxinming820@gmail.com>
> L: linux-wireless@vger.kernel.org
> S: Maintained
> F: drivers/net/wireless/marvell/mwifiex/
>
> I'm very close of marking this driver as orphan unless anyone steps up.
> This is not how to maintain a driver.
I'd be fully on board with removing these maintainers, as I don't recall
hearing from any of them in years. (In fact, some of these addresses
don't have a single mail logged on lore.kernel.org/all/...) I just
didn't want to be the one to say it.
On the other hand, I regularly look at pretty much anything for mwifiex,
as long as the submitter is in relatively good faith. So I wouldn't mind
being a Reviewer (or Maintainer? what's the difference, when Kalle
does the committing anyway?). And that might qualify as "Odd Fixes", as
I don't plan on doing much more than keeping the lights on.
I'll submit the MAINTAINERS patch if you'd like.
Brian
next prev parent reply other threads:[~2023-07-20 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 2:37 [PATCH v3] wifi: mwifiex: Fix OOB and integer underflow when rx packets pinkperfect
[not found] ` <CAKNAPeOvG1MVD0y5xuZpN8mSEzvrzcvRhdyrTJhju-_Z1nGV0g@mail.gmail.com>
2023-07-13 17:56 ` Jakub Kicinski
2023-07-20 6:55 ` Kalle Valo
2023-07-20 15:08 ` Jakub Kicinski
2023-07-20 17:14 ` Brian Norris [this message]
2023-07-21 7:15 ` Kalle Valo
2023-07-21 23:07 ` Brian Norris
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=ZLlrd4dDz+kA5l18@google.com \
--to=briannorris@chromium.org \
--cc=amitkarwar@gmail.com \
--cc=ganapathi017@gmail.com \
--cc=huxinming820@gmail.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pinkperfect2021@gmail.com \
--cc=sharvari.harisangam@nxp.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).