From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>
Cc: netfilter-devel@vger.kernel.org,
Arturo Borrero Gonzalez <arturo@netfilter.org>
Subject: Re: [nft PATCH v4 0/3] Fix printing of range elements in named sets
Date: Wed, 19 Jul 2017 19:16:29 +0200 [thread overview]
Message-ID: <20170719171629.GA18828@salvia> (raw)
In-Reply-To: <20170719130529.25398-1-phil@nwl.cc>
On Wed, Jul 19, 2017 at 03:05:26PM +0200, Phil Sutter wrote:
> This is v4 of 'nft monitor' fixes for range elements. Apart from
> changing the new flag's location in struct expr as requested, this
> series now also covers mappings.
Series applied, thanks Phil!
prev parent reply other threads:[~2017-07-19 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 13:05 [nft PATCH v4 0/3] Fix printing of range elements in named sets Phil Sutter
2017-07-19 13:05 ` [nft PATCH v2 1/3] segtree: Introduce flag for half-open range elements Phil Sutter
2017-07-19 13:05 ` [nft PATCH v3 2/3] monitor: Fix printing of range elements in named sets Phil Sutter
2017-07-19 17:17 ` Pablo Neira Ayuso
2017-07-19 18:22 ` Phil Sutter
2017-07-19 13:05 ` [nft PATCH v2 3/3] tests: Add basic monitor testing framework Phil Sutter
2017-07-19 17:16 ` Pablo Neira Ayuso [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=20170719171629.GA18828@salvia \
--to=pablo@netfilter.org \
--cc=arturo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.