From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Harish Patil <harish.patil@cavium.com>,
Rasesh Mody <rasesh.mody@cavium.com>,
Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
Qi Zhang <qi.z.zhang@intel.com>,
Xiao Wang <xiao.w.wang@intel.com>,
Beilei Xing <beilei.xing@intel.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
Shahed Shaikh <shahed.shaikh@cavium.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
Yong Wang <yongwang@vmware.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v2 1/2] drivers/net: fix icc deprecated parameter warning
Date: Fri, 13 Apr 2018 23:30:36 +0100 [thread overview]
Message-ID: <785d2341-aa1d-eb65-65eb-bb1072cdba4f@intel.com> (raw)
In-Reply-To: <20180413222109.144181-1-ferruh.yigit@intel.com>
On 4/13/2018 11:21 PM, Ferruh Yigit wrote:
> With icc (ICC) 18.0.1 20171018, -wd usage generates following warning:
>
> icc: command line remark #10010: option '-wd3656' is deprecated and will
> be removed in a future release. See '-help deprecated'
>
> "icc -help deprecated" output is:
> -wd use -diag-disable
>
> Based on above information "-wd" converted to "-diag-disable"
>
> Cc: stable@dpdk.org
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> Tested-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-04-13 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180312123900.22361-1-ferruh.yigit@intel.com>
2018-03-12 12:39 ` [dpdk-stable] [PATCH 2/2] drivers/net: remove redundant icc flag Ferruh Yigit
2018-04-11 10:12 ` [dpdk-stable] [dpdk-dev] " De Lara Guarch, Pablo
2018-04-13 22:21 ` [dpdk-stable] [PATCH v2 1/2] drivers/net: fix icc deprecated parameter warning Ferruh Yigit
2018-04-13 22:21 ` [dpdk-stable] [PATCH v2 2/2] drivers/net: remove redundant icc flag Ferruh Yigit
2018-04-13 22:30 ` Ferruh Yigit [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=785d2341-aa1d-eb65-65eb-bb1072cdba4f@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=harish.patil@cavium.com \
--cc=konstantin.ananyev@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=rasesh.mody@cavium.com \
--cc=shahed.shaikh@cavium.com \
--cc=stable@dpdk.org \
--cc=wenzhuo.lu@intel.com \
--cc=xiao.w.wang@intel.com \
--cc=yongwang@vmware.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).