From: Paolo Abeni <pabeni@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>, netdev@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [GIT PULL] wireless-next-2026-01-29
Date: Thu, 29 Jan 2026 15:08:46 +0100 [thread overview]
Message-ID: <b0d6887f-7946-46b6-986a-bf410b832d66@redhat.com> (raw)
In-Reply-To: <20260129110136.176980-39-johannes@sipsolutions.net>
On 1/29/26 11:58 AM, Johannes Berg wrote:
> Here's another set of changes for net-next. Two things to note:
>
> 1) This introduces a couple of new sparse warnings, because it
> cannot deal with guard(spinlock_bh)() which the drivers are
> now using. I previously fixed sparse for that for RCU, but
> given the context tracking work will remove this validation
> from sparse entirely, I haven't bothered trying to keep up.
>
> 2) There's a core SDIO patch in here, but that's intentional
> and we agreed with the maintainer to merge it through this
> tree since only two wireless changes depend on it.
>
> Please pull and let us know if there's any problem.
The CI also report a 32bit build failure, but with a dangling link to
the actual build results:
https://patchwork.kernel.org/project/netdevbpf/patch/20260129110136.176980-39-johannes@sipsolutions.net/
so it could be a CI flake, but could you please have a look?
/P
next prev parent reply other threads:[~2026-01-29 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 10:58 [GIT PULL] wireless-next-2026-01-29 Johannes Berg
2026-01-29 14:08 ` Paolo Abeni [this message]
2026-01-29 14:20 ` Johannes Berg
2026-01-30 7:22 ` Ping-Ke Shih
2026-01-30 8:18 ` Johannes Berg
2026-01-29 16:28 ` Jakub Kicinski
2026-01-30 4:25 ` 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=b0d6887f-7946-46b6-986a-bf410b832d66@redhat.com \
--to=pabeni@redhat.com \
--cc=johannes@sipsolutions.net \
--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