From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
Harish Patil <harish.patil@cavium.com>,
Rasesh Mody <rasesh.mody@cavium.com>,
"Rahul Lakkireddy" <rahul.lakkireddy@chelsio.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
"Wang, Xiao W" <xiao.w.wang@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
Shahed Shaikh <shahed.shaikh@cavium.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
Shrikrishna Khare <skhare@vmware.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] drivers/net: update icc deprecated parameter
Date: Wed, 11 Apr 2018 10:11:11 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CCD08FD@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20180312123900.22361-1-ferruh.yigit@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ferruh Yigit
> Sent: Monday, March 12, 2018 12:39 PM
> To: Harish Patil <harish.patil@cavium.com>; Rasesh Mody
> <rasesh.mody@cavium.com>; Rahul Lakkireddy
> <rahul.lakkireddy@chelsio.com>; Lu, Wenzhuo <wenzhuo.lu@intel.com>;
> Zhang, Qi Z <qi.z.zhang@intel.com>; Wang, Xiao W <xiao.w.wang@intel.com>;
> Xing, Beilei <beilei.xing@intel.com>; Ananyev, Konstantin
> <konstantin.ananyev@intel.com>; Shahed Shaikh
> <shahed.shaikh@cavium.com>; Andrew Rybchenko
> <arybchenko@solarflare.com>; Shrikrishna Khare <skhare@vmware.com>
> Cc: dev@dpdk.org; Yigit, Ferruh <ferruh.yigit@intel.com>
> Subject: [dpdk-dev] [PATCH 1/2] drivers/net: update icc deprecated parameter
>
> 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"
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
Should this go into the stable branch? These warnings will be present there too.
Apart from this comment:
Tested-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
next prev parent reply other threads:[~2018-04-11 10:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 12:38 Ferruh Yigit
2018-03-12 12:39 ` [dpdk-dev] [PATCH 2/2] drivers/net: remove redundant icc flag Ferruh Yigit
2018-04-11 10:12 ` De Lara Guarch, Pablo
2018-04-11 10:11 ` De Lara Guarch, Pablo [this message]
2018-04-11 10:46 ` [dpdk-dev] [PATCH 1/2] drivers/net: update icc deprecated parameter Ferruh Yigit
2018-04-13 22:21 ` [dpdk-dev] [PATCH v2 1/2] drivers/net: fix icc deprecated parameter warning Ferruh Yigit
2018-04-13 22:21 ` [dpdk-dev] [PATCH v2 2/2] drivers/net: remove redundant icc flag Ferruh Yigit
2018-04-13 22:30 ` [dpdk-dev] [PATCH v2 1/2] drivers/net: fix icc deprecated parameter warning Ferruh Yigit
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=E115CCD9D858EF4F90C690B0DCB4D8976CCD08FD@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=arybchenko@solarflare.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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=skhare@vmware.com \
--cc=wenzhuo.lu@intel.com \
--cc=xiao.w.wang@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).