From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, David Hunt <david.hunt@intel.com>
Cc: dev@dpdk.org, liang.j.ma@intel.com, lei.a.yao@intel.com
Subject: Re: [dpdk-dev] [PATCH] examples/l3fwd-power: fix build with icc
Date: Fri, 26 Oct 2018 23:13:23 +0100 [thread overview]
Message-ID: <c52426e2-0d21-a26d-6c28-b6978bb87b10@intel.com> (raw)
In-Reply-To: <20181026220045.28739-1-thomas@monjalon.net>
On 10/26/2018 11:00 PM, Thomas Monjalon wrote:
> main.c(376): error #592: variable "lcore_id" is used before its value is set
> RTE_SET_USED(lcore_id);
> ^
>
> The variables were voided with RTE_SET_USED without an obvious reason.
> Removing these voidings should avoid the icc error.
>
> Fixes: a137d012 ("examples/l3fwd-power: support traffic pattern aware control")
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
Tested-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2018-10-26 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 22:00 Thomas Monjalon
2018-10-26 22:13 ` Ferruh Yigit [this message]
2018-10-26 23:24 ` 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=c52426e2-0d21-a26d-6c28-b6978bb87b10@intel.com \
--to=ferruh.yigit@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=lei.a.yao@intel.com \
--cc=liang.j.ma@intel.com \
--cc=thomas@monjalon.net \
/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).