From: Hangbin Liu <liuhangbin@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net 0/4] wireguard fixes for 6.17-rc6
Date: Tue, 16 Sep 2025 01:03:44 +0000 [thread overview]
Message-ID: <aMi3cB7Epg-I7tMn@fedora> (raw)
In-Reply-To: <20250910013644.4153708-1-Jason@zx2c4.com>
On Wed, Sep 10, 2025 at 03:36:40AM +0200, Jason A. Donenfeld wrote:
> Hi Jakub,
>
> Please find three small fixes to wireguard:
>
> 1) A general simplification to the way wireguard chooses the next
> available cpu, by making use of cpumask_nth(), and covering an edge
> case.
>
> 2) A cleanup to the selftests kconfig.
>
> 3) A fix to the selftests kconfig so that it actually runs again.
Hi Jason,
Sorry to bother you, but I have a WireGuard self-test update [1] that has been
stuck in "Awaiting Upstream" for a long time without any comments. Could you
please help review it?
[1] https://lore.kernel.org/netdev/20250527032635.10361-1-liuhangbin@gmail.com
Thanks
Hangbin
prev parent reply other threads:[~2025-09-16 1:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 1:36 [PATCH net 0/4] wireguard fixes for 6.17-rc6 Jason A. Donenfeld
2025-09-10 1:36 ` [PATCH net 1/4] wireguard: queueing: simplify wg_cpumask_next_online() Jason A. Donenfeld
2025-09-10 1:36 ` [PATCH net 2/4] wireguard: queueing: always return valid online CPU in wg_cpumask_choose_online() Jason A. Donenfeld
2025-09-10 1:36 ` [PATCH net 3/4] wireguard: selftests: remove CONFIG_SPARSEMEM_VMEMMAP=y from qemu kernel config Jason A. Donenfeld
2025-09-10 1:36 ` [PATCH net 4/4] wireguard: selftests: select CONFIG_IP_NF_IPTABLES_LEGACY Jason A. Donenfeld
2025-09-11 2:20 ` [PATCH net 0/4] wireguard fixes for 6.17-rc6 Jakub Kicinski
2025-09-14 19:07 ` Jason A. Donenfeld
2025-09-12 2:00 ` patchwork-bot+netdevbpf
2025-09-16 1:03 ` Hangbin Liu [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=aMi3cB7Epg-I7tMn@fedora \
--to=liuhangbin@gmail.com \
--cc=Jason@zx2c4.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).