From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Martin Kaiser <martin@kaiser.cx>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Phillip Potter <phil@philpotter.co.uk>,
Michael Straube <straube.linux@gmail.com>,
Pavel Skripkin <paskripkin@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] staging: r8188eu: clean up OnDisassoc
Date: Wed, 30 Nov 2022 19:20:17 +0100 [thread overview]
Message-ID: <a9f7f851-af2e-a0e1-adb9-d7cac6c0c57f@gmail.com> (raw)
In-Reply-To: <20221129205152.128172-1-martin@kaiser.cx>
On 11/29/22 21:51, Martin Kaiser wrote:
> Clean up the OnDisassoc function. Use a struct ieee80211_mgmt for parsing
> the incoming message and reduce the indentation levels.
>
> Please apply this after the two series I sent some days ago
>
> Martin Kaiser (5):
> staging: r8188eu: use ieee80211_mgmt to parse addresses
> staging: r8188eu: read reason code from ieee80211_mgmt
> staging: r8188eu: move bBusyTraffic update
> staging: r8188eu: handle the non-ap case first
> staging: r8188eu: simplify err handling for unknown station
>
> drivers/staging/r8188eu/core/rtw_mlme_ext.c | 47 ++++++++++-----------
> 1 file changed, 22 insertions(+), 25 deletions(-)
>
Tested-by: Philipp Hortmann <philipp.g.hortmann@gmail.com> # Edimax N150
prev parent reply other threads:[~2022-11-30 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 20:51 Martin Kaiser
2022-11-29 20:51 ` [PATCH 1/5] staging: r8188eu: use ieee80211_mgmt to parse addresses Martin Kaiser
2022-11-29 20:51 ` [PATCH 2/5] staging: r8188eu: read reason code from ieee80211_mgmt Martin Kaiser
2022-11-29 20:51 ` [PATCH 3/5] staging: r8188eu: move bBusyTraffic update Martin Kaiser
2022-11-29 20:51 ` [PATCH 4/5] staging: r8188eu: handle the non-ap case first Martin Kaiser
2022-11-29 20:51 ` [PATCH 5/5] staging: r8188eu: simplify err handling for unknown station Martin Kaiser
2022-11-30 18:20 ` Philipp Hortmann [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=a9f7f851-af2e-a0e1-adb9-d7cac6c0c57f@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=martin@kaiser.cx \
--cc=paskripkin@gmail.com \
--cc=phil@philpotter.co.uk \
--cc=straube.linux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®