From: Jakub Kicinski <kuba@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [GIT PULL] wireless-2026-09-30
Date: Wed, 30 Sep 2026 14:19:01 -0700 [thread overview]
Message-ID: <20260930141901.618c04f3@kernel.org> (raw)
In-Reply-To: <20260930124440.224799-3-johannes@sipsolutions.net>
On Wed, 30 Sep 2026 14:43:00 +0200 Johannes Berg wrote:
> Things aren't really slowing down by that much, unfortunately, but
> these are mostly fairlyh obvious changes.
FWIW Linus started pushing back on the PR sizes last week.
So we gotta be more judicious going forward. I think you were already
more judicious than us in general, but keep that we got warned in mind.
I spotted some probe/remove fixes here (wlcore, iwlegacy etc), I tend
to queue anything like that to -next these days, those are infinite.
Potentially also the Tx status reporting ? (AFAIU that'd imply a
malicious device.)
All of that only if you have spare mental capacity.
Otherwise just ignore and keep doing what you're doing.
next prev parent reply other threads:[~2026-09-30 21:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 12:43 [GIT PULL] wireless-2026-09-30 Johannes Berg
2026-09-30 21:19 ` Jakub Kicinski [this message]
2026-09-30 21:20 ` 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=20260930141901.618c04f3@kernel.org \
--to=kuba@kernel.org \
--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