From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [libnftnl PATCH v2] expr: Introduce nftnl_expr_fprintf()
Date: Tue, 17 Oct 2017 14:02:22 +0200 [thread overview]
Message-ID: <20171017120222.GW32305@orbyte.nwl.cc> (raw)
In-Reply-To: <20171017113150.GA8818@salvia>
Hi,
Actually, I don't quite get the suggested change:
On Tue, Oct 17, 2017 at 01:31:50PM +0200, Pablo Neira Ayuso wrote:
> @@ -308,3 +307,7 @@ global:
>
> local: *;
> };
> +
> +LIBNFTNL_6 {
> + nftnl_expr_fprintf;
> +} LIBMNL_5;
Why LIBMNL_5? Shouldn't this be LIBNFTNL_5?
Cheers, Phil
next prev parent reply other threads:[~2017-10-17 12:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 21:36 [libnftnl PATCH] expr: Introduce nftnl_expr_fprintf() Phil Sutter
2017-10-17 11:05 ` Pablo Neira Ayuso
2017-10-17 11:22 ` [libnftnl PATCH v2] " Phil Sutter
2017-10-17 11:31 ` Pablo Neira Ayuso
2017-10-17 11:54 ` Phil Sutter
2017-10-17 12:02 ` Phil Sutter [this message]
2017-10-17 12:11 ` Pablo Neira Ayuso
2017-10-17 13:17 ` [libnftnl PATCH v3] " Phil Sutter
2017-10-17 13:19 ` Pablo Neira Ayuso
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=20171017120222.GW32305@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).