netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>
Cc: Eric Leblond <eric@regit.org>,
	netfilter-devel@vger.kernel.org, Florian Westphal <fw@strlen.de>
Subject: Re: [nft PATCH v2 0/4] libnftables preparations
Date: Tue, 24 Oct 2017 17:20:33 +0200	[thread overview]
Message-ID: <20171024152033.GA31888@salvia> (raw)
In-Reply-To: <20171023153319.13415-1-phil@nwl.cc>

[-- Attachment #1: Type: text/plain, Size: 579 bytes --]

On Mon, Oct 23, 2017 at 05:33:15PM +0200, Phil Sutter wrote:
> The following series prepares libnftables libarary split-off by moving
> API functions into src/libnftables.c, introducing
> include/nftables/nftables.h and enhancing the code by a number of
> getters and setters for applications to change configurable parts of
> struct nft_ctx without knowledge of that struct's internals.
> 
> The 'nft' binary will become the first "demo" user of libnftables and
> acts as a reference for library design and usability.

Series applied.

I have to merged this patch below to 1/4.

[-- Attachment #2: x.patch --]
[-- Type: text/x-diff, Size: 367 bytes --]

diff --git a/configure.ac b/configure.ac
index b01c5bdef0eb..099a4a5e81ec 100644
--- a/configure.ac
+++ b/configure.ac
@@ -140,6 +140,7 @@ AC_CONFIG_FILES([					\
 		Makefile				\
 		src/Makefile				\
 		include/Makefile			\
+		include/nftables/Makefile		\
 		include/linux/Makefile			\
 		include/linux/netfilter/Makefile	\
 		include/linux/netfilter_arp/Makefile	\

  parent reply	other threads:[~2017-10-24 15:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-23 15:33 [nft PATCH v2 0/4] libnftables preparations Phil Sutter
2017-10-23 15:33 ` [nft PATCH v2 1/4] libnftables: Move library stuff out of main.c Phil Sutter
2017-10-24 15:48   ` Pablo Neira Ayuso
2017-10-24 16:42     ` Phil Sutter
2017-11-09 13:25     ` [nft PATCH] libnftables: Unexport enum nftables_exit_codes Phil Sutter
2017-11-09 19:27       ` Phil Sutter
2017-11-10 11:27         ` [nft PATCH v2] " Phil Sutter
2017-11-13 12:31           ` Pablo Neira Ayuso
2017-11-13 12:38             ` Phil Sutter
2017-11-13 14:08               ` [nft PATCH v3] " Phil Sutter
2017-11-16 13:33                 ` Pablo Neira Ayuso
2017-11-16 13:48                   ` Phil Sutter
2017-11-13 13:49             ` [nft PATCH v2] " Phil Sutter
2017-11-13 13:53               ` Pablo Neira Ayuso
2017-11-13 14:04                 ` Phil Sutter
2017-10-23 15:33 ` [nft PATCH v2 2/4] libnftables: Introduce nft_ctx_flush_cache() Phil Sutter
2017-10-24 15:52   ` Pablo Neira Ayuso
2017-10-24 17:40     ` Phil Sutter
2017-10-25  9:25       ` Pablo Neira Ayuso
2017-10-25 11:40         ` [nft PATCH] libnftables: Get rid of explicit cache flushes Phil Sutter
2017-10-26 18:15           ` Pablo Neira Ayuso
2017-10-23 15:33 ` [nft PATCH v2 3/4] cli: Use nft_run_cmd_from_buffer() Phil Sutter
2017-10-23 15:33 ` [nft PATCH v2 4/4] libnftables: Introduce getters and setters for everything Phil Sutter
2017-10-24 15:20 ` Pablo Neira Ayuso [this message]
2017-10-24 16:29   ` [nft PATCH v2 0/4] libnftables preparations Phil Sutter

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=20171024152033.GA31888@salvia \
    --to=pablo@netfilter.org \
    --cc=eric@regit.org \
    --cc=fw@strlen.de \
    --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 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).