From: Phil Sutter <phil@nwl.cc>
To: netfilter-devel@vger.kernel.org
Subject: Re: [iptables PATCH v2 0/3] Chain counter fixes here and there
Date: Thu, 10 Aug 2023 14:16:02 +0200 [thread overview]
Message-ID: <ZNTVAnjB+b+7bEGf@orbyte.nwl.cc> (raw)
In-Reply-To: <20230810112325.20630-1-phil@nwl.cc>
On Thu, Aug 10, 2023 at 01:23:22PM +0200, Phil Sutter wrote:
> Resending patch 2 after the test I created for it in patch 3 exposed the
> iptables-nft bug fixed in patch 1.
>
> Phil Sutter (3):
> nft: Create builtin chains with counters enabled
> Revert "libiptc: fix wrong maptype of base chain counters on restore"
> tests: shell: Test chain policy counter behaviour
Series applied.
prev parent reply other threads:[~2023-08-10 12:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 11:23 [iptables PATCH v2 0/3] Chain counter fixes here and there Phil Sutter
2023-08-10 11:23 ` [iptables PATCH v2 1/3] nft: Create builtin chains with counters enabled Phil Sutter
2023-08-10 11:23 ` [iptables PATCH v2 2/3] Revert "libiptc: fix wrong maptype of base chain counters on restore" Phil Sutter
2023-08-10 11:23 ` [iptables PATCH v2 3/3] tests: shell: Test chain policy counter behaviour Phil Sutter
2023-08-10 12:16 ` Phil Sutter [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=ZNTVAnjB+b+7bEGf@orbyte.nwl.cc \
--to=phil@nwl.cc \
--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;
as well as URLs for NNTP newsgroup(s).