From: Kalle Valo <kvalo@codeaurora.org>
To: Martin Fuzzey <martin.fuzzey@flowbird.group>
Cc: linux-wireless@vger.kernel.org,
Amitkumar Karwar <amitkarwar@gmail.com>,
Siva Rebbagondla <siva8118@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
Prameela Rani Garnepudi <prameela.j04cs@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] rsi: fix startup and P2P mode
Date: Tue, 21 Sep 2021 08:49:05 +0300 [thread overview]
Message-ID: <875yuuwka6.fsf@codeaurora.org> (raw)
In-Reply-To: <1630337206-12410-1-git-send-email-martin.fuzzey@flowbird.group> (Martin Fuzzey's message of "Mon, 30 Aug 2021 17:26:43 +0200")
Martin Fuzzey <martin.fuzzey@flowbird.group> writes:
> This series fixes an occasional startup failure when BT
> coexistence is enabled and makes P2P mode work
> (the two are unrelated but sending as a series since the same files
> are modified).
>
> Tested on RS9116 in P2P client mode against an Android phone (S8, Android 9)
>
> For an unknown reason GO mode does not work against the phone but it
> does work against a second RS9116 device.
> In this case Android does not send a response to the 3rd WPA handshake
> packet. It is difficult to debug this without the phone wpa_supplicant
> logs which I don't have.
>
> Regression tested OK for STA and AP modes.
>
> V2:
> * rebase against wireless-drivers-next
> * add cc: stable to patches 2 & 3
>
> Martin Fuzzey (3):
> rsi: fix occasional initialisation failure with BT coex
> rsi: fix key enabled check causing unwanted encryption for vap_id > 0
> rsi: fix rate mask set leading to P2P failure
BTW thanks for the outstanding cover letter and commit logs in the
patches, it was so easy for me to understand the background and the
level of testing these patches have had. If everyone would write their
patches like this my job would be a lot easier :)
I'm going to use this patchset as an example in the submittingpatches
wiki page.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2021-09-21 5:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 15:26 [PATCH v2 0/3] rsi: fix startup and P2P mode Martin Fuzzey
2021-08-30 15:26 ` [PATCH v2 1/3] rsi: fix occasional initialisation failure with BT coex Martin Fuzzey
2021-09-21 5:43 ` Kalle Valo
2021-08-30 15:26 ` [PATCH v2 2/3] rsi: fix key enabled check causing unwanted encryption for vap_id > 0 Martin Fuzzey
2021-08-30 15:26 ` [PATCH v2 3/3] rsi: fix rate mask set leading to P2P failure Martin Fuzzey
2021-09-21 5:49 ` Kalle Valo [this message]
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=875yuuwka6.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=amitkarwar@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.fuzzey@flowbird.group \
--cc=prameela.j04cs@gmail.com \
--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.