DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
	"Zhu, TaoX" <taox.zhu@intel.com>,
	"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
	"Wu, Jingjing" <jingjing.wu@intel.com>,
	"Iremonger, Bernard" <bernard.iremonger@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"ivan.ilchenko@oktetlabs.com" <ivan.ilchenko@oktetlabs.com>
Subject: Re: [dpdk-dev] [PATCH v2] app/testpmd: fix unused variable compile error
Date: Thu, 26 Sep 2019 11:04:30 +0100	[thread overview]
Message-ID: <419b994d-7b78-5c56-798e-c04cba470222@intel.com> (raw)
In-Reply-To: <039ED4275CED7440929022BC67E7061153D9DD64@SHSMSX105.ccr.corp.intel.com>

On 9/26/2019 2:33 AM, Zhang, Qi Z wrote:
> 
> 
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of taox.zhu@intel.com
>> Sent: Thursday, September 26, 2019 2:03 AM
>> To: Lu, Wenzhuo <wenzhuo.lu@intel.com>; Wu, Jingjing
>> <jingjing.wu@intel.com>; Iremonger, Bernard <bernard.iremonger@intel.com>
>> Cc: dev@dpdk.org; ivan.ilchenko@oktetlabs.com; Zhu, TaoX
>> <taox.zhu@intel.com>
>> Subject: [dpdk-dev] [PATCH v2] app/testpmd: fix unused variable compile error
>>
>> From: Zhu Tao <taox.zhu@intel.com>
>>
>> This minor patch fixes unused variable ‘ret’ compile error When
>> CONFIG_RTE_LIBRTE_I40E_16BYTE_RX_DESC was selected.
>>
>> Fixes: f5267e485a2a ("app/testpmd: check status of getting ethdev info")
>>
>> Signed-off-by: Zhu Tao <taox.zhu@intel.com>
> 
> Reviewed-by: Qi Zhang <qi.z.zhang@intel.com>
> 

Applied to dpdk-next-net/master, thanks.

      reply	other threads:[~2019-09-26 10:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25 17:54 [dpdk-dev] [DPDK] " taox.zhu
2019-09-25 10:34 ` Andrew Rybchenko
2019-09-25 18:03 ` [dpdk-dev] [PATCH v2] " taox.zhu
2019-09-26  1:33   ` Zhang, Qi Z
2019-09-26 10:04     ` 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=419b994d-7b78-5c56-798e-c04cba470222@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=ivan.ilchenko@oktetlabs.com \
    --cc=jingjing.wu@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=taox.zhu@intel.com \
    --cc=wenzhuo.lu@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).