From: Andrew Rybchenko <arybchenko@solarflare.com>
To: <taox.zhu@intel.com>, <wenzhuo.lu@intel.com>,
<jingjing.wu@intel.com>, <bernard.iremonger@intel.com>
Cc: <dev@dpdk.org>, <ivan.ilchenko@oktetlabs.com>
Subject: Re: [dpdk-dev] [DPDK] app/testpmd: fix unused variable compile error
Date: Wed, 25 Sep 2019 13:34:33 +0300 [thread overview]
Message-ID: <1154e1a0-2ca1-72e7-dda7-2a230a408e2b@solarflare.com> (raw)
In-Reply-To: <20190925175400.62253-1-taox.zhu@intel.com>
On 9/25/19 8:54 PM, taox.zhu@intel.com wrote:
> 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: Andrew Rybchenko <arybchenko@solarflare.com>
Thanks.
next prev parent reply other threads:[~2019-09-25 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 17:54 taox.zhu
2019-09-25 10:34 ` Andrew Rybchenko [this message]
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
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=1154e1a0-2ca1-72e7-dda7-2a230a408e2b@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=ivan.ilchenko@oktetlabs.com \
--cc=jingjing.wu@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).