From: Florian Westphal <fw@strlen.de>
To: netfilter-devel@vger.kernel.org
Subject: [ANN] nf-next remains OPEN
Date: Wed, 11 Feb 2026 13:00:56 +0100 [thread overview]
Message-ID: <aYxveCxwSezABhIa@strlen.de> (raw)
Hello,
while net-next remains closed until Feb 23rd, I would like to keep
nf-next open for new features.
So, if you had changes targetting nf-next that aren't in the
patchwork backlog[1] anymore, please consider resubmitting them.
I have queued the 'commit mutex deadlock during reset' series to
nf:testing, no need to send it again.
Thanks.
[1] https://patchwork.ozlabs.org/project/netfilter-devel/list/
reply other threads:[~2026-02-11 12:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=aYxveCxwSezABhIa@strlen.de \
--to=fw@strlen.de \
--cc=netfilter-devel@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