From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: add architecture specific rte_cpuflags.c files
Date: Wed, 27 Jan 2016 18:52:25 +0100 [thread overview]
Message-ID: <5530206.lovNufpa2q@xps13> (raw)
In-Reply-To: <1447149727-14034-1-git-send-email-ferruh.yigit@intel.com>
2015-11-10 10:02, Ferruh Yigit:
> --- a/lib/librte_eal/linuxapp/eal/rte_eal_version.map
> +++ b/lib/librte_eal/linuxapp/eal/rte_eal_version.map
> @@ -133,5 +133,6 @@ DPDK_2.2 {
> global:
>
> rte_intr_cap_multiple;
> + cpu_feature_table;
As it is now an exported symbol, it should be prefixed with rte_.
Please take care when rebasing to
- create a new block of symbols for the new release version,
- and keep the new flag for AVX512 which is going to be applied.
next prev parent reply other threads:[~2016-01-27 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 10:02 Ferruh Yigit
2016-01-27 17:52 ` Thomas Monjalon [this message]
2016-01-28 12:20 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2016-02-02 10:20 ` Thomas Monjalon
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=5530206.lovNufpa2q@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).