All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Ganslandt <alexander.ganslandt@axis.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH v2 3/3] station: improve roam scan strategy
Date: Fri, 12 Sep 2025 09:53:13 +0200	[thread overview]
Message-ID: <60359dd3-7a50-4cc5-9523-4ca8347eab81@axis.com> (raw)
In-Reply-To: <b69729a6-808d-4b92-a244-d148af40c7ad@gmail.com>

On 9/9/25 15:35, James Prestwood wrote:
> Overall I agree with this approach, but I'm still looking at this patch 
> in detail as its quite intrusive to the roaming logic. One thing to 
> address right off the bat is the CI failure. Looks like there were some 
> incremental patch issues (applying patches 1-by-1 and building in 
> between). This prevented the autotests from running but I suspect we 
> will need to alter the autotests a bit due to logic changes in this patch.
> 
> Thanks,
> 
> James

Hello James,

Thanks for the feedback! Yes, a lot of core roaming logic has changed, 
so it's good that we take our time to ensure it works well. I found it a 
bit tricky to follow all the paths where scans would be triggered so I 
tried to make all roads lead to station_start_roam(). If I succeeded 
with that in a good way is up for debate :)

I will push a fix for your comment and the CI issues soon!

Thanks again,
Alexander


      reply	other threads:[~2025-09-12  7:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-29  7:43 [PATCH v2 0/3] Improve roam scan strategy Alexander Ganslandt
2025-08-29  7:43 ` [PATCH v2 1/3] util: add scan_freq_set_size function Alexander Ganslandt
2025-08-29  7:43 ` [PATCH v2 2/3] station: improve scan_freqs_order channel subsets Alexander Ganslandt
2025-09-09 13:25   ` James Prestwood
2025-08-29  7:43 ` [PATCH v2 3/3] station: improve roam scan strategy Alexander Ganslandt
2025-09-09 13:35   ` James Prestwood
2025-09-12  7:53     ` Alexander Ganslandt [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=60359dd3-7a50-4cc5-9523-4ca8347eab81@axis.com \
    --to=alexander.ganslandt@axis.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 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.