Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: jeff.chen_1@oss.nxp.com, linux-wireless@vger.kernel.org
Subject: Re: pull-request: nxpwifi-fixes-20261006
Date: Mon, 05 Oct 2026 21:17:29 +0200	[thread overview]
Message-ID: <8234429838b276fdf1eaa54da32c4b32347ed361.camel@sipsolutions.net> (raw)
In-Reply-To: <20261005171814.2884772-1-jeff.chen_1@oss.nxp.com>

Hi,

You based this on wireless-next, I cannot pull this.

> nxpwifi updates for 7.3-rc7

Ideally -rc6, but I'm not really sure it's worth mentioning what you're
aiming for anyway ;-)

> This update contains fixes for station list synchronization,
> aggregation and reorder buffer cleanup, authentication frame
> handling, and several memory safety issues.
> 
> Highlights:
> - fix concurrent sta_list add/delete races
> - clean up station entries on uAP deauthentication
> - fix Tx BA stream entry deletion logic
> - avoid deleting Rx reorder entries under RCU
> - improve aggregation buffer cleanup
> - fix authentication frame length validation
> - handle authentication frame allocation failures
> - fix wakeup timer shutdown ordering
> 
> ----------------------------------------------------------------
> David Carlier (2):
>       wifi: nxpwifi: fix inverted check in Tx BA stream entry deletion
>       wifi: nxpwifi: do not delete Rx reorder entries under RCU
> 
> Linmao Li (7):
>       wifi: nxpwifi: protect sta_list against concurrent add and delete
>       wifi: nxpwifi: delete the station entry on the uAP deauth event
>       wifi: nxpwifi: wait for the wakeup timer before the adapter is freed
>       wifi: nxpwifi: free the aggregation buffer when the RA list disappears
>       wifi: nxpwifi: zero the channel statistics array
>       wifi: nxpwifi: fix the authentication frame length handling
>       wifi: nxpwifi: handle authentication frame allocation failures

I guess I'll (when you send a new version) pull this and try to convince
net to take it, but Jakub pushed back because Linus pushed back, and you
really can't just send a single pull request late in the cycle this day
and age. You _need_ to send more pull requests and earlier, especially
now that we get so many fixes. Yes it's only seven patches now, but some
have been pending for almost two months, and Felix has *36* patches (if
I pull that). It adds up quickly. Please send things during earlier RCs.

johannes

  reply	other threads:[~2026-10-05 19:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 17:18 pull-request: nxpwifi-fixes-20261006 jeff.chen_1
2026-10-05 19:17 ` Johannes Berg [this message]
2026-10-05 19:21   ` Johannes Berg
  -- strict thread matches above, loose matches on Subject: below --
2026-10-06 13:57 jeff.chen_1

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=8234429838b276fdf1eaa54da32c4b32347ed361.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=jeff.chen_1@oss.nxp.com \
    --cc=linux-wireless@vger.kernel.org \
    /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