From: Kalle Valo <kvalo@kernel.org>
To: Marek Vasut <marex@denx.de>
Cc: linux-wireless@vger.kernel.org, Angus Ainslie <angus@akkea.ca>,
Jakub Kicinski <kuba@kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
Martin Fuzzey <martin.fuzzey@flowbird.group>,
Martin Kepplinger <martink@posteo.de>,
Prameela Rani Garnepudi <prameela.j04cs@gmail.com>,
Sebastian Krzyszkowiak <sebastian.krzyszkowiak@puri.sm>,
Siva Rebbagondla <siva8118@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH v5] wifi: rsi: Fix handling of 802.3 EAPOL frames sent via control port
Date: Mon, 14 Nov 2022 14:57:15 +0200 [thread overview]
Message-ID: <87iljhbsno.fsf@kernel.org> (raw)
In-Reply-To: <da2bca7b-1289-747c-df11-fb424381c6e6@denx.de> (Marek Vasut's message of "Sun, 13 Nov 2022 19:59:36 +0100")
Marek Vasut <marex@denx.de> writes:
> On 11/10/22 06:39, Kalle Valo wrote:
>
>> Marek Vasut <marex@denx.de> writes:
>>
>>> On 11/9/22 17:20, Kalle Valo wrote:
>>>
>>>> That's a pity indeed. Should we at least mark the driver as orphaned in
>>>> MAINTAINERS?
>>>>
>>>> Or even better if you Marek would be willing to step up as the
>>>> maintainer? :)
>>>
>>> I think best mark it orphaned, to make it clear what the state of the
>>> driver really is.
>>>
>>> If RSI was willing to provide documentation, or at least releases
>>> which are not 30k+/20k- single-all-in-one-commit dumps of code, or at
>>> least any help, I would consider it. But not like this.
>>
>> Yeah, very understandable. So let's mark the driver orphaned then, can
>> someone send a patch?
>
> Done
Great, thank you very much.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-11-14 12:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 16:33 [PATCH v5] wifi: rsi: Fix handling of 802.3 EAPOL frames sent via control port Marek Vasut
2022-11-07 12:37 ` Kalle Valo
2022-11-07 13:23 ` Marek Vasut
2022-11-07 13:54 ` Kalle Valo
2022-11-07 14:44 ` Marek Vasut
2022-11-07 16:50 ` Fuzzey, Martin
2022-11-09 16:20 ` Kalle Valo
2022-11-09 18:17 ` Marek Vasut
2022-11-10 5:39 ` Kalle Valo
2022-11-13 18:59 ` Marek Vasut
2022-11-14 12:57 ` Kalle Valo [this message]
2022-11-08 7:41 ` Kalle Valo
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=87iljhbsno.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=angus@akkea.ca \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marex@denx.de \
--cc=martin.fuzzey@flowbird.group \
--cc=martink@posteo.de \
--cc=netdev@vger.kernel.org \
--cc=prameela.j04cs@gmail.com \
--cc=sebastian.krzyszkowiak@puri.sm \
--cc=siva8118@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.