From: "Alvin Šipraga" <ALSI@bang-olufsen.dk>
To: Denis Kenzior <denkenz@gmail.com>
Cc: "iwd@lists.linux.dev" <iwd@lists.linux.dev>
Subject: Re: [PATCH 11/11] netdev: disambiguate between disconnection types
Date: Sat, 25 Nov 2023 20:57:26 +0000 [thread overview]
Message-ID: <bmsflmybfnfjdnbkvjkk3rforvhmjitapyotzzwtl2wo6wlpfh@fj5cj5ixicpu> (raw)
In-Reply-To: <f25e7bcb-3990-4d72-b51d-b197f8c40a64@gmail.com>
Hi Denis,
On Fri, Nov 24, 2023 at 10:25:40AM -0600, Denis Kenzior wrote:
> Hi Alvin,
>
> > > Distinguish between 1 and 2/3 by having the disconnect procedure take
> > > different paths. For now there are no functional changes since all
> > > paths end up in netdev_connect_failed(), but this will change in the
> > > future.
> >
> > Sorry for not following up on the issue I raised the other week. I am
> > catching up with the mailing list now and see this patch. Am I right to
> > assume this is some preperatory work for solving the issue I identified?
>
> Yep. I got side-tracked by some oFono work, so don't have a fix for your
> particular problem yet.
Great, thanks a lot for following up on this. Sorry that I did not send
out a more robust patch, but I have not had time these days.
Please add me on CC if you work further on this and we can do some
additional internal testing to see if it works.
Kind regards,
Alvin
next prev parent reply other threads:[~2023-11-25 20:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 17:14 [PATCH 01/11] netdev: Fix obtaining reason code from deauth frames Denis Kenzior
2023-11-14 17:14 ` [PATCH 02/11] netdev: sa_query: Fix reason code handling Denis Kenzior
2023-11-14 17:14 ` [PATCH 03/11] netdev: Use CMD_DISCONNECT if OCI fails Denis Kenzior
2023-11-14 17:14 ` [PATCH 04/11] netdev: Don't unnecessarily call netdev_connect_failed Denis Kenzior
2023-11-14 17:14 ` [PATCH 05/11] netdev: Move CMD_DISCONNECT builder to nl80211util Denis Kenzior
2023-11-14 17:14 ` [PATCH 06/11] netdev: Move CMD_DEAUTHENTICATE " Denis Kenzior
2023-11-14 17:14 ` [PATCH 07/11] netdev: Move CMD_DEL_STATION " Denis Kenzior
2023-11-14 17:14 ` [PATCH 08/11] netdev: Move pairwise NEW_KEY " Denis Kenzior
2023-11-14 17:14 ` [PATCH 09/11] netdev: Move CMD_NEW_KEY RX-only " Denis Kenzior
2023-11-14 17:14 ` [PATCH 10/11] netdev: Move CMD_REKEY_OFFLOAD " Denis Kenzior
2023-11-14 17:14 ` [PATCH 11/11] netdev: disambiguate between disconnection types Denis Kenzior
2023-11-14 17:39 ` James Prestwood
2023-11-14 20:09 ` Denis Kenzior
2023-11-14 20:11 ` James Prestwood
2023-11-24 12:20 ` Alvin Šipraga
2023-11-24 16:25 ` Denis Kenzior
2023-11-25 20:57 ` Alvin Šipraga [this message]
2023-11-14 20:48 ` [PATCH 01/11] netdev: Fix obtaining reason code from deauth frames Denis Kenzior
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=bmsflmybfnfjdnbkvjkk3rforvhmjitapyotzzwtl2wo6wlpfh@fj5cj5ixicpu \
--to=alsi@bang-olufsen.dk \
--cc=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).