From: Johannes Berg <johannes@sipsolutions.net>
To: Kuniyuki Iwashima <kuniyu@google.com>, Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [GIT PULL] wireless-next-2026-10-07
Date: Thu, 08 Oct 2026 17:01:47 +0200 [thread overview]
Message-ID: <8575c0d3cf58e56300313482dd1d4d74cbdbf4f0.camel@sipsolutions.net> (raw)
In-Reply-To: <2688563455012eb80063ae014f78230b10a14710.camel@sipsolutions.net>
On Thu, 2026-10-08 at 09:44 +0200, Johannes Berg wrote:
> > Also, I hope we could remove the long comment in __rtnl_unlock().
>
> Couldn't we remove that today, by just __rtnl_unlock() in that place in
> cfg80211? But it's not exported, for good reason, presumably.
>
> But that's also irrelevant, because indeed after my patchset cfg80211
> doesn't do that any more:
> https://lore.kernel.org/linux-wireless/20261006100655.2687533-21-johannes@sipsolutions.net/
>
FWIW, I double-checked and didn't find any other code in wifi that would
do the rtnl_lock(); lock(); rtnl_unlock() ... unlock(); thing, so that
really is gone once I merge that series (which I'm planning to do after
all the net-next pulls net etc. settling this week).
johannes
next prev parent reply other threads:[~2026-10-08 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 20:57 [GIT PULL] wireless-next-2026-10-07 Johannes Berg
2026-10-07 23:36 ` Jakub Kicinski
2026-10-08 2:05 ` Kuniyuki Iwashima
2026-10-08 7:44 ` Johannes Berg
2026-10-08 15:01 ` Johannes Berg [this message]
2026-10-09 21:24 ` Kuniyuki Iwashima
2026-10-07 23:40 ` 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=8575c0d3cf58e56300313482dd1d4d74cbdbf4f0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--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