From: "Gajdzica, MaciejX T" <maciejx.t.gajdzica@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>,
"nhorman@tuxdriver.com" <nhorman@tuxdriver.com>
Subject: [dpdk-dev] Issue with rte_compat versioning macros
Date: Fri, 19 Jun 2015 14:38:08 +0000 [thread overview]
Message-ID: <9CC680510C0AC140A846FED2EF7F96281383E81B@IRSMSX102.ger.corp.intel.com> (raw)
Hi
There is an issue with macros in rte_compat.h. For shared library case, macro BIND_DEFAULT_SYMBOL
takes three arguments and for other case it takes only two arguments. Also letters for macro variable names
are not consistent in these two cases.
Best Regards
Maciek
next reply other threads:[~2015-06-19 14:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 14:38 Gajdzica, MaciejX T [this message]
2015-06-19 14:48 ` Thomas Monjalon
2015-06-19 15:04 ` Gajdzica, MaciejX T
2015-06-19 15:32 ` Neil Horman
2015-06-22 15:32 ` Gajdzica, MaciejX T
2015-06-22 16:51 ` Neil Horman
2015-06-23 7:45 ` Gajdzica, MaciejX T
2015-06-23 11:28 ` Gajdzica, MaciejX T
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=9CC680510C0AC140A846FED2EF7F96281383E81B@IRSMSX102.ger.corp.intel.com \
--to=maciejx.t.gajdzica@intel.com \
--cc=dev@dpdk.org \
--cc=nhorman@tuxdriver.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).