From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Alvaro Neira Ayuso <alvaroneay@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [libnftnl PATCH 2/4 v2] src: add support to import json/xml with the new syntax
Date: Fri, 30 Jan 2015 19:38:18 +0100 [thread overview]
Message-ID: <20150130183818.GB22598@salvia> (raw)
In-Reply-To: <1422628525-28109-2-git-send-email-alvaroneay@gmail.com>
On Fri, Jan 30, 2015 at 03:35:23PM +0100, Alvaro Neira Ayuso wrote:
> diff --git a/src/libnftnl.map b/src/libnftnl.map
> index be7b998..d999046 100644
> --- a/src/libnftnl.map
> +++ b/src/libnftnl.map
> @@ -182,8 +182,13 @@ global:
> nft_ruleset_attr_unset;
> nft_ruleset_attr_set;
> nft_ruleset_attr_get;
> + nft_ruleset_ctx_is_set;
> + nft_ruleset_ctx_get;
> + nft_ruleset_ctx_get_u32;
> nft_ruleset_parse;
> nft_ruleset_parse_file;
> + nft_ruleset_parse_file_cb;
> + nft_ruleset_parse_buffer_cb;
> nft_ruleset_snprintf;
> nft_ruleset_fprintf;
You cannot place these new symbols here. You have to add new symbols
to a new section as I explained in patch 1/4.
next prev parent reply other threads:[~2015-01-30 18:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 14:35 [libnftnl PATCH 1/4 v2] src: add command tag in json/xml export support Alvaro Neira Ayuso
2015-01-30 14:35 ` [libnftnl PATCH 2/4 v2] src: add support to import json/xml with the new syntax Alvaro Neira Ayuso
2015-01-30 18:38 ` Pablo Neira Ayuso [this message]
2015-01-30 19:56 ` Pablo Neira Ayuso
2015-01-30 14:35 ` [libnftnl PATCH 3/4 v4] example: Parse and create netlink message using the new parsing functions Alvaro Neira Ayuso
2015-01-30 19:43 ` Pablo Neira Ayuso
2015-01-30 14:35 ` [libnftnl PATCH 4/4 v2] test: update json/xml tests to the new syntax Alvaro Neira Ayuso
2015-01-30 18:38 ` Pablo Neira Ayuso
2015-01-30 18:36 ` [libnftnl PATCH 1/4 v2] src: add command tag in json/xml export support 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=20150130183818.GB22598@salvia \
--to=pablo@netfilter.org \
--cc=alvaroneay@gmail.com \
--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).