From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: "Dai, Wei" <wei.dai@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Dai, Wei" <wei.dai@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] app/testpmd: fix commands to config some offload
Date: Thu, 2 Aug 2018 09:11:31 +0000 [thread overview]
Message-ID: <8CEF83825BEC744B83065625E567D7C260CD2665@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <1533173520-6623-1-git-send-email-wei.dai@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Wei Dai
> Sent: Thursday, August 2, 2018 2:32 AM
> To: Wu, Jingjing <jingjing.wu@intel.com>; Lu, Wenzhuo
> <wenzhuo.lu@intel.com>
> Cc: dev@dpdk.org; Dai, Wei <wei.dai@intel.com>; stable@dpdk.org
> Subject: [dpdk-dev] [PATCH] app/testpmd: fix commands to config some offload
>
> Without this patch, testpmd command to config Rx offload keep_crc would fail
> and report "Bad argument".
> This patch aslo fix the command to config the Tx offload mbuf_fast_free.
>
> Fixes: 70815c9ecadd ("ethdev: add new offload flag to keep CRC")
> Fixes: c73a9071877a ("app/testpmd: add commands to test new offload API")
> Cc: stable@dpdk.org
>
> Signed-off-by: Wei Dai <wei.dai@intel.com>
> Tested-by: Yuan Peng <yuan.peng@intel.com>
Should have been [PATCH v2] otherwise fine.
Acked-by: Bernard Iremonger <Bernard.iremonger@intel.com>
next prev parent reply other threads:[~2018-08-02 9:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 3:45 [dpdk-stable] " Wei Dai
2018-07-24 14:22 ` [dpdk-stable] [dpdk-dev] " Iremonger, Bernard
2018-08-02 1:41 ` Dai, Wei
2018-07-25 3:29 ` Peng, Yuan
2018-08-02 1:32 ` [dpdk-stable] " Wei Dai
2018-08-02 9:11 ` Iremonger, Bernard [this message]
2018-08-03 12:53 ` [dpdk-stable] [dpdk-dev] " Dai, Wei
2018-08-03 12:55 ` [dpdk-stable] [PATCH v3] " Wei Dai
2018-08-05 10:41 ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
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=8CEF83825BEC744B83065625E567D7C260CD2665@IRSMSX107.ger.corp.intel.com \
--to=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=stable@dpdk.org \
--cc=wei.dai@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).