public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
	"Korenblit, Miriam Rachel" <miriam.rachel.korenblit@intel.com>
Subject: Re: [GIT PULL] wireless-next-2025-06-25
Date: Wed, 25 Jun 2025 19:40:30 +0200	[thread overview]
Message-ID: <32bc4c358dcf9f7ae2ccc30b38d9aee61014a92a.camel@sipsolutions.net> (raw)
In-Reply-To: <20250625102555.35d3509a@kernel.org>

On Wed, 2025-06-25 at 10:25 -0700, Jakub Kicinski wrote:
> On Wed, 25 Jun 2025 14:00:22 +0200 Johannes Berg wrote:
> > And for -next quite a bit more, but not all that much
> > that really stands out either. iwlwifi picked up a bunch
> > of really old cleanups from patchwork "spring" cleaning,
> > and the rest just move along with regularly scheduled
> > feature additions. No known merge conflicts here either.
> > 
> > Please pull and let us know if there's any problem.
> 
> Hm, cocci points out a real bug here I think:
> 
> drivers/net/wireless/intel/iwlwifi/pcie/gen1_2/trans-gen2.c:550:2-8: preceding lock on line 496
> 
> Not major enough to delay pulling tho..

Hmm, sorry about that, I _know_ I fixed this after the kernel robot
and/or Dan reported it, but looks like Miri didn't put it in yet.

It actually exists in wireless/net too though, just the file moved now
in -next so maybe that's why it was reported (again). We'll have to fix
it in wireless and the merge should sort out the file move.

johannes

  reply	other threads:[~2025-06-25 17:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-25 12:00 [GIT PULL] wireless-next-2025-06-25 Johannes Berg
2025-06-25 17:25 ` Jakub Kicinski
2025-06-25 17:40   ` Johannes Berg [this message]
2025-06-25 17:41 ` patchwork-bot+netdevbpf

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=32bc4c358dcf9f7ae2ccc30b38d9aee61014a92a.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=miriam.rachel.korenblit@intel.com \
    --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