From: pasichdev <apasichnik9@gmail.com>
To: "Jason A . Donenfeld" <Jason@zx2c4.com>,
netdev@vger.kernel.org, wireguard@lists.zx2c4.com
Cc: Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net] wireguard: peer: free packets left on the per-peer queues on removal
Date: Sat, 24 Oct 2026 00:16:26 +0300 [thread overview]
Message-ID: <20261023211626.99784-1-apasichnik9@gmail.com> (raw)
In-Reply-To: <20261003201625.4572-1-apasichnik9@gmail.com>
From: Andrii Pasichnyk <apasichnik9@gmail.com>
Hi Jason,
Gentle ping on this one. Patchwork shows it as awaiting upstream, so I
assume it should go through your tree. It still applies to net and
net-next unchanged; if you would rather have it taken through net
directly, or want anything changed, please let me know.
Thanks,
Andrii
next prev parent reply other threads:[~2026-10-23 21:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 20:16 [PATCH net] wireguard: peer: free packets left on the per-peer queues on removal Andrii Pasichnyk
2026-10-03 20:19 ` netdev-bot+sinfo
2026-10-03 20:41 ` Andrii Pasichnyk
2026-10-23 21:16 ` pasichdev [this message]
2026-10-23 22:58 ` Jason A. Donenfeld
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=20261023211626.99784-1-apasichnik9@gmail.com \
--to=apasichnik9@gmail.com \
--cc=Jason@zx2c4.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wireguard@lists.zx2c4.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