From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
"John W. Linville" <linville@tuxdriver.com>,
"Legacy, Allain (Wind River)" <allain.legacy@windriver.com>,
"Peters, Matt (Wind River)" <matt.peters@windriver.com>,
Harish Patil <harish.patil@cavium.com>,
"Rasesh Mody" <rasesh.mody@cavium.com>,
Stephen Hurd <stephen.hurd@broadcom.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
"Doherty, Declan" <declan.doherty@intel.com>,
Marcin Wojtas <mw@semihalf.com>,
Michal Krawczyk <mk@semihalf.com>,
Guy Tzalik <gtzalik@amazon.com>,
Evgeny Schemeilin <evgenys@amazon.com>,
John Daley <johndale@cisco.com>,
Nelson Escobar <neescoba@cisco.com>,
"Chen, Jing D" <jing.d.chen@intel.com>,
"Zhang, Helin" <helin.zhang@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
Pascal Mazon <pascal.mazon@6wind.com>,
"Yuanhan Liu" <yuanhan.liu@linux.intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Shrikrishna Khare <skhare@vmware.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] driver/net: remove unnecessary macro for unused variables
Date: Mon, 15 May 2017 00:53:11 +0000 [thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09093B5B842A@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20170512103303.93161-1-ferruh.yigit@intel.com>
Hi,
> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Friday, May 12, 2017 6:33 PM
> To: John W. Linville; Legacy, Allain (Wind River); Peters, Matt (Wind River);
> Harish Patil; Rasesh Mody; Stephen Hurd; Ajit Khaparde; Doherty, Declan; Lu,
> Wenzhuo; Marcin Wojtas; Michal Krawczyk; Guy Tzalik; Evgeny Schemeilin;
> John Daley; Nelson Escobar; Chen, Jing D; Zhang, Helin; Wu, Jingjing; Ananyev,
> Konstantin; Andrew Rybchenko; Pascal Mazon; Yuanhan Liu; Maxime
> Coquelin; Shrikrishna Khare
> Cc: dev@dpdk.org; Yigit, Ferruh
> Subject: [PATCH] driver/net: remove unnecessary macro for unused variables
>
> remove __rte_unused instances that are not required.
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
next prev parent reply other threads:[~2017-05-15 0:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 10:33 Ferruh Yigit
2017-05-12 11:39 ` Legacy, Allain
2017-05-15 0:53 ` Lu, Wenzhuo [this message]
2017-05-15 10:33 ` Ferruh Yigit
2017-05-15 2:31 ` Yuanhan Liu
2017-05-15 8:42 ` Ferruh Yigit
2017-05-15 9:17 ` Ferruh Yigit
2017-05-15 9:19 ` Yuanhan Liu
2017-05-15 9:26 ` Ferruh Yigit
2017-05-15 9:24 ` Yuanhan Liu
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=6A0DE07E22DDAD4C9103DF62FEBC09093B5B842A@shsmsx102.ccr.corp.intel.com \
--to=wenzhuo.lu@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=allain.legacy@windriver.com \
--cc=arybchenko@solarflare.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=evgenys@amazon.com \
--cc=ferruh.yigit@intel.com \
--cc=gtzalik@amazon.com \
--cc=harish.patil@cavium.com \
--cc=helin.zhang@intel.com \
--cc=jing.d.chen@intel.com \
--cc=jingjing.wu@intel.com \
--cc=johndale@cisco.com \
--cc=konstantin.ananyev@intel.com \
--cc=linville@tuxdriver.com \
--cc=matt.peters@windriver.com \
--cc=maxime.coquelin@redhat.com \
--cc=mk@semihalf.com \
--cc=mw@semihalf.com \
--cc=neescoba@cisco.com \
--cc=pascal.mazon@6wind.com \
--cc=rasesh.mody@cavium.com \
--cc=skhare@vmware.com \
--cc=stephen.hurd@broadcom.com \
--cc=yuanhan.liu@linux.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).