netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: pull-request: wireless-next-2024-02-20
Date: Wed, 21 Feb 2024 14:35:31 -0800	[thread overview]
Message-ID: <20240221143531.56942c6e@kernel.org> (raw)
In-Reply-To: <20240220165842.917CDC433F1@smtp.kernel.org>

On Tue, 20 Feb 2024 16:58:42 +0000 (UTC) Kalle Valo wrote:
> Hi,
> 
> here's a pull request to net-next tree, more info below. Please let me know if
> there are any problems.
> 
> Kalle
> 
> The following changes since commit b7198383ef2debe748118996f627452281cf27d7:
> 
>   wifi: iwlwifi: mvm: fix a crash when we run out of stations (2024-02-08 14:55:39 +0100)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git tags/wireless-next-2024-02-20
> 
> for you to fetch changes up to dd66185c23f71af36397bebfc99ede608dca07b6:
> 
>   wifi: wilc1000: add missing read critical sections around vif list traversal (2024-02-19 18:21:36 +0200)
> 
> ----------------------------------------------------------------
> wireless-next patches for v6.9
> 
> The second "new features" pull request for v6.9.  Lots of iwlwifi and
> stack changes this time. And naturally smaller changes to other drivers.
> 
> We also twice merged wireless into wireless-next to avoid conflicts
> between the trees.
> 
> Major changes:
> 
> stack
> 
> * mac80211: negotiated TTLM request support
> 
> * SPP A-MSDU support
> 
> * mac80211: wider bandwidth OFDMA config support
> 
> iwlwifi
> 
> * kunit tests
> 
> * bump FW API to 89 for AX/BZ/SC devices
> 
> * enable SPP A-MSDUs
> 
> * support for new devices
> 
> ath12k
> 
> * refactoring in preparation for Multi-Link Operation (MLO) support
> 
> * 1024 Block Ack window size support
> 
> * provide firmware wmi logs via a trace event
> 
> ath11k
> 
> * 36 bit DMA mask support
> 
> * support 6 GHz station power modes: Low Power Indoor (LPI), Standard
>   Power) SP and Very Low Power (VLP)
> 
> rtl8xxxu
> 
> * TP-Link TL-WN823N V2 support

I'm getting these on a normal (i.e. non-W=1) clang build today:

../drivers/net/wireless/ath/ath12k/mac.c:8000:9: warning: variable 'ret' is uninitialized when used here [-Wuninitialized]
 8000 |         return ret;
      |                ^~~
../drivers/net/wireless/ath/ath12k/mac.c:7962:9: note: initialize the variable 'ret' to silence this warning
 7962 |         int ret, i, j;
      |                ^
      |                 = 0

  parent reply	other threads:[~2024-02-21 22:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20 16:58 pull-request: wireless-next-2024-02-20 Kalle Valo
2024-02-20 17:03 ` Kalle Valo
2024-02-21 11:51 ` patchwork-bot+netdevbpf
2024-02-21 22:35 ` Jakub Kicinski [this message]
2024-02-21 23:34   ` Jeff Johnson
2024-02-22  1:18     ` Jeff Johnson
2024-02-22  1:25       ` Jakub Kicinski
2024-02-22  5:11         ` Kalle Valo
2024-02-22 10:59           ` Kalle Valo
2024-02-22 23:17             ` Jakub Kicinski

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=20240221143531.56942c6e@kernel.org \
    --to=kuba@kernel.org \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).