From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: netfilter@vger.kernel.org
Subject: nftables 1.0.6.y stable branch updates (strike 2)
Date: Fri, 1 Aug 2025 01:16:21 +0200 [thread overview]
Message-ID: <aIv5RcJY6RycFRFc@calendula> (raw)
In-Reply-To: <Z5J7Vh5OPORkmmXC@calendula>
Hi,
I have updated the 1.0.6.y -stable branch:
https://git.netfilter.org/nftables/log/?h=1.0.6.y
This branch contains 334 selected commits out of the 887 commits
available between v1.0.6 and git HEAD.
I have backported tests/shell and tests/py based on git HEAD on this
branch, so this stable branch is self-contained.
- tests/shell displays:
I: results: [OK] 428 [SKIPPED] 23 [FAILED] 0 [TOTAL] 451
- tests/py: No errors. This includes -j for json testing.
I have tested with libnftnl 1.2.4 and Linux kernel 6.1-stable.
I might still collect a few more recent fixes in git HEAD from the
last two months.
Proposed plan is to release this -stable 1.0.6.y after nftables 1.1.4
comes out, in the first two weeks of Aug 2025.
next parent reply other threads:[~2025-07-31 23:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Z5J7Vh5OPORkmmXC@calendula>
2025-07-31 23:16 ` Pablo Neira Ayuso [this message]
2025-08-17 21:54 ` nftables 1.0.6.y stable branch updates (strike 2) Pablo Neira Ayuso
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=aIv5RcJY6RycFRFc@calendula \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@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;
as well as URLs for NNTP newsgroup(s).