From: patchwork-bot+netdevbpf@kernel.org
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [GIT PULL] wireless-next-2026-05-28
Date: Fri, 29 May 2026 00:12:01 +0000 [thread overview]
Message-ID: <178001352190.1565998.2039430206651171575.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260528123911.284536-26-johannes@sipsolutions.net>
Hello:
This pull request was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 28 May 2026 14:37:26 +0200 you wrote:
> Hi,
>
> Here's a new set of changes, mostly ath and iwlwifi
> drivers this time.
>
> I have a few more things pending, and I expect a few
> more drivers will have pull requests later too.
>
> [...]
Here is the summary with links:
- [GIT,PULL] wireless-next-2026-05-28
https://git.kernel.org/netdev/net-next/c/e7d6bd24e883
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-05-29 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 12:37 [GIT PULL] wireless-next-2026-05-28 Johannes Berg
2026-05-29 0:12 ` patchwork-bot+netdevbpf [this message]
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=178001352190.1565998.2039430206651171575.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@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