From: Alexander Dahl via ptxdist <ptxdist@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Alexander Dahl <ada@thorsis.com>
Subject: [ptxdist] [PATCH 0/2] netfilter: version bumps
Date: Mon, 20 Apr 2026 16:39:15 +0200 [thread overview]
Message-ID: <20260420143917.1592314-1-ada@thorsis.com> (raw)
Not sure about those new configure options of nftables which seem for
development and maintainer:
Both --disable-fuzzer and --enable-fuzzer lead to reporting 'fuzzer
support: yes' . Omitting either of them hides the line from configure
output. I have a feeling printing 'yes' when passing --disable-fuzzer
is not intended? However I can not see any difference at runtime.
And I can not make any sense of --with-stable-release at all.
Greets
Alex
Alexander Dahl (2):
libnftnl: version bump 1.2.8 -> 1.3.1
nftables: version bump 1.1.1 -> 1.1.6
rules/libnftnl.make | 4 ++--
rules/nftables.make | 9 ++++++---
2 files changed, 8 insertions(+), 5 deletions(-)
base-commit: 9e28c99dd6a5b30c578b75deb71bd82d41fda429
--
2.47.3
next reply other threads:[~2026-04-20 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 14:39 Alexander Dahl via ptxdist [this message]
2026-04-20 14:39 ` [ptxdist] [PATCH 1/2] libnftnl: version bump 1.2.8 -> 1.3.1 Alexander Dahl via ptxdist
2026-04-20 14:39 ` [ptxdist] [PATCH 2/2] nftables: version bump 1.1.1 -> 1.1.6 Alexander Dahl via ptxdist
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=20260420143917.1592314-1-ada@thorsis.com \
--to=ptxdist@pengutronix.de \
--cc=ada@thorsis.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