public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH 1/4] blacklist: rename ROAM_REQUESTED to AP_BUSY
Date: Mon, 19 May 2025 16:39:14 -0500	[thread overview]
Message-ID: <ecc4cbfd-49e3-42ba-b0bd-224dbbc6aad0@gmail.com> (raw)
In-Reply-To: <20250519163624.198865-1-prestwoj@gmail.com>

Hi James,

On 5/19/25 11:36 AM, James Prestwood wrote:
> The initial pass of this feature only envisioned BSS transition
> management frames as the trigger to "roam blacklist" a BSS, hence
> the original name. But some APs actually utilize status codes that
> also indicate to the stations that they are busy, or not able to
> handle more connections. This directly aligns with the original
> motivation of the "roam blacklist" series and these events should
> also trigger this type of blacklist.
> 
> First, since we will be applying this blacklist to cases other
> than being told to roam, rename this reason code internally to
> BLACKLIST_REASON_AP_BUSY. The config option is also being renamed
> to [Blacklist].InitialAccessPointBusyTimeout while also supporting
> the old config option, but warning that it is deprecated.
> ---
>   src/blacklist.c | 20 ++++++++++++++------
>   src/blacklist.h | 12 +++++++-----
>   src/station.c   |  5 ++---
>   3 files changed, 23 insertions(+), 14 deletions(-)
> 

All applied, thanks.

Regards,
-Denis

      parent reply	other threads:[~2025-05-19 21:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-19 16:36 [PATCH 1/4] blacklist: rename ROAM_REQUESTED to AP_BUSY James Prestwood
2025-05-19 16:36 ` [PATCH 2/4] docs: replace/deprecate InitialRoamRequestedTimeout James Prestwood
2025-05-19 16:36 ` [PATCH 3/4] station: utilize the AP_BUSY blacklist for denied auth/assoc James Prestwood
2025-05-19 16:36 ` [PATCH 4/4] auto-t: use renamed InitialAccessPointBusyTimeout James Prestwood
2025-05-19 21:39 ` Denis Kenzior [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=ecc4cbfd-49e3-42ba-b0bd-224dbbc6aad0@gmail.com \
    --to=denkenz@gmail.com \
    --cc=iwd@lists.linux.dev \
    --cc=prestwoj@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