From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Peng, Yuan" <yuan.peng@intel.com>,
"Zhao1, Wei" <wei.zhao1@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
Bernard Iremonger <bernard.iremonger@intel.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] app/testpmd: fix Rx offload search error
Date: Wed, 7 Nov 2018 19:02:24 +0000 [thread overview]
Message-ID: <eee6ecf3-6c5e-ce5d-c180-e8cfe9dba6b0@intel.com> (raw)
In-Reply-To: <67D543A150B29E4CAAE53918F64EDAEA376471EF@SHSMSX103.ccr.corp.intel.com>
On 11/7/2018 7:58 AM, Peng, Yuan wrote:
<...>
> From: Zhao1, Wei
> Sent: Wednesday, November 7, 2018 2:14 PM
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Peng, Yuan <yuan.peng@intel.com>; Lu, Wenzhuo <wenzhuo.lu@intel.com>; Zhao1, Wei <wei.zhao1@intel.com>
> Subject: [PATCH] app/testpmd: fix Rx offload search error
>
> There is an error in function in function search_rx_offload(), it will break when get unexpected return value from function rte_eth_dev_rx_offload_name(), but rte_eth_dev_rx_offload_name() will return some unexpected value indead.
>
> Fixes: c73a9071877a ("app/testpmd: add commands to test new offload API")
> Signed-off-by: Wei Zhao <wei.zhao1@intel.com>
>
> Tested-by: Peng, Yuan <yuan.peng@intel.com>
Applied to dpdk-next-net/master, thanks.
(checkpatch issues reported by Bernard fixed while merging.)
next prev parent reply other threads:[~2018-11-07 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 6:14 [dpdk-dev] " Wei Zhao
2018-11-07 7:58 ` Peng, Yuan
2018-11-07 17:09 ` Iremonger, Bernard
2018-11-07 19:02 ` Ferruh Yigit [this message]
2018-11-08 1:30 ` [dpdk-dev] [dpdk-stable] " Zhao1, Wei
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=eee6ecf3-6c5e-ce5d-c180-e8cfe9dba6b0@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=wei.zhao1@intel.com \
--cc=wenzhuo.lu@intel.com \
--cc=yuan.peng@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).