From: Kalle Valo <kvalo@kernel.org>
To: Marek Vasut <marex@denx.de>
Cc: linux-wireless@vger.kernel.org,
Amitkumar Karwar <amit.karwar@redpinesignals.com>,
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, 07 Nov 2022 15:54:52 +0200 [thread overview]
Message-ID: <877d06g98z.fsf@kernel.org> (raw)
In-Reply-To: <7a3b6d5c-1d73-1d31-434f-00703c250dd6@denx.de> (Marek Vasut's message of "Mon, 7 Nov 2022 14:23:37 +0100")
Marek Vasut <marex@denx.de> writes:
>> BTW did you test this on a real device?
>
> Yes, SDIO RS9116 on next-20221104 and 5.10.153 .
Very good, thanks.
> What prompts this question ?
I get too much "fixes" which have been nowhere near real hardware and
can break the driver instead of fixing anything, especially syzbot
patches have been notorious. So I have become cautious.
--
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-07 13:55 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 [this message]
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
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=877d06g98z.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=amit.karwar@redpinesignals.com \
--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.