From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [libnftnl PATCH] Rename xfree() to libnftnl_xfree() to avoid symbol naming conflict
Date: Wed, 20 Aug 2014 14:07:05 +0200 [thread overview]
Message-ID: <20140820140705.26f64dbb@free-electrons.com> (raw)
In-Reply-To: <20140819220236.GA7136@salvia>
Dear Pablo Neira Ayuso,
On Wed, 20 Aug 2014 00:02:36 +0200, Pablo Neira Ayuso wrote:
> > To solve this, this patch renames the libnftnl xfree() function to
> > libnftnl_xfree().
>
> Would this small patch solve your problem too?
Yes, I believe this would work as well, as long as this definition
doesn't get exposed to public headers of the library.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-08-20 12:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 13:39 [libnftnl PATCH] Rename xfree() to libnftnl_xfree() to avoid symbol naming conflict Thomas Petazzoni
2014-08-19 22:02 ` Pablo Neira Ayuso
2014-08-20 12:07 ` Thomas Petazzoni [this message]
2014-08-20 13:00 ` Jan Engelhardt
2014-08-20 13:22 ` 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=20140820140705.26f64dbb@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.