From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH RFC 0/4] Implement --echo option
Date: Thu, 27 Jul 2017 17:02:52 +0200 [thread overview]
Message-ID: <20170727150252.GR2235@orbyte.nwl.cc> (raw)
In-Reply-To: <20170727142622.12029-1-phil@nwl.cc>
On Thu, Jul 27, 2017 at 04:26:18PM +0200, Phil Sutter wrote:
> Long description of what it is and how it works in patch 3. Patches 1
> and 2 are dependencies to patch 3.
>
> The whole thing is RFC, mainly because of NFT_MSG_META_ECHO which
> doesn't quite belong to where it is but I didn't find a better way to
> reuse monitor callbacks for the job at hand.
>
> Feedback highly appreciated, of course!
Crap! I just found some unstaged changes in my tree which belong to this
series. Will send a v2 soon. Sorry for the mess.
Cheers, Phil
prev parent reply other threads:[~2017-07-27 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 14:26 [nft PATCH RFC 0/4] Implement --echo option Phil Sutter
2017-07-27 14:26 ` [nft PATCH RFC 1/4] mnl: Consolidate mnl_batch_talk() parameters Phil Sutter
2017-07-27 14:26 ` [nft PATCH RFC 2/4] netlink: Pass nlmsg flags from rule.c Phil Sutter
2017-07-27 14:26 ` [nft PATCH RFC 3/4] Implement --echo option Phil Sutter
2017-07-27 14:26 ` [nft PATCH RFC 4/4] tests: Add a simple test suite for " Phil Sutter
2017-07-27 15:02 ` 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=20170727150252.GR2235@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).