From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Vijay Subramanian <subramanian.vijay@gmail.com>
Cc: netfilter-devel@vger.kernel.org, kaber@trash.net,
Aaron Conole <aconole@redhat.com>
Subject: Re: [PATCH libnftnl] Fix compilation with JSON and XML parsing enabled
Date: Mon, 12 Oct 2015 18:14:52 +0200 [thread overview]
Message-ID: <20151012161452.GA31001@salvia> (raw)
In-Reply-To: <1444418467-18610-1-git-send-email-subramanian.vijay@gmail.com>
On Fri, Oct 09, 2015 at 12:21:07PM -0700, Vijay Subramanian wrote:
> Fix missing/incorrect variables.
> Also remove unsed variables to avoid warnings.
Applied this with minor nit.
> Signed-off-by: Vijay Subramanian <subramanian.vijay@gmail.com>
> ---
> src/expr/dup.c | 13 +++++--------
> src/expr/limit.c | 2 +-
> 2 files changed, 6 insertions(+), 9 deletions(-)
>
> diff --git a/src/expr/dup.c b/src/expr/dup.c
> index d0fa35f..217450a 100644
> --- a/src/expr/dup.c
> +++ b/src/expr/dup.c
> @@ -115,18 +115,16 @@ static int nftnl_expr_dup_json_parse(struct nftnl_expr *e, json_t *root,
> struct nftnl_parse_err *err)
> {
> #ifdef JSON_PARSING
> - struct nftnl_expr_dup *dup = nftnl_expr_data(e);
> uint32_t sreg_addr, sreg_dev;
> - int datareg_type;
> + int ret = 0;
No need to initialize this, it will be override by next function call.
> - ret = nftnl_jansson_parse_val(root, "sreg_addr", NFT_TYPE_U32, &sreg_addr, err);
> + ret = nftnl_jansson_parse_val(root, "sreg_addr", NFTNL_TYPE_U32, &sreg_addr, err);
prev parent reply other threads:[~2015-10-12 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 19:21 [PATCH libnftnl] Fix compilation with JSON and XML parsing enabled Vijay Subramanian
2015-10-09 20:08 ` Aaron Conole
2015-10-09 20:11 ` Aaron Conole
2015-10-09 22:08 ` Vijay Subramanian
2015-10-12 16:14 ` 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=20151012161452.GA31001@salvia \
--to=pablo@netfilter.org \
--cc=aconole@redhat.com \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=subramanian.vijay@gmail.com \
/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).