test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Wan, Zhe" <zhe.wan@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Wan, Zhe" <zhe.wan@intel.com>
Subject: Re: [dts] [PATCH V1] test_plans/rxtx_callbacks: test plan revise
Date: Wed, 3 Apr 2019 17:07:47 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA5B60B@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1553628956-147741-1-git-send-email-zhe.wan@intel.com>

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Zhe
> Sent: Tuesday, March 26, 2019 12:36 PM
> To: dts@dpdk.org
> Cc: Wan, Zhe <zhe.wan@intel.com>
> Subject: [dts] [PATCH V1] test_plans/rxtx_callbacks: test plan revise
> 
> From: Zhe Wan <zhe.wan@intel.com>
> 
> Signed-off-by: Zhe Wan <zhe.wan@intel.com>
> ---
>  test_plans/rxtx_callbacks_test_plan.rst | 12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/test_plans/rxtx_callbacks_test_plan.rst
> b/test_plans/rxtx_callbacks_test_plan.rst
> index d8687bb..e1c2ce6 100644
> --- a/test_plans/rxtx_callbacks_test_plan.rst
> +++ b/test_plans/rxtx_callbacks_test_plan.rst
> @@ -46,7 +46,7 @@ prior to transmission to calculate the elapsed time, in
> CPU cycles.
>  Running the Application
>  =======================
> 
> -Open common_base and set ``CONFIG_RTE_ETHDEV_RXTX_CALLBACKS=y``.
> +Set ``CONFIG_RTE_ETHDEV_RXTX_CALLBACKS=y`` in config/common_base.
> 
>  To run the example in a ``linuxapp`` environment::
> 
> @@ -55,10 +55,10 @@ To run the example in a ``linuxapp`` environment::
>  Refer to *DPDK Getting Started Guide* for general information on running
> applications and the Environment Abstraction Layer (EAL) options.
> 
> -test_rxtx_callbacks
> -===================
> +Test Case:rxtx callbacks
> +==========================
> 
> -Running::
> +Run the example::
> 
>       ./examples/rxtx_callbacks/build/rxtx_callbacks -c 2 -n 4
> 
> @@ -66,5 +66,5 @@ waked up:::
> 
>       Core X forwarding packets.
> 
> -Send one packet on Port0,check the port1 receive packet.
> -It receive one packet that the port0 send.
> +Send one packet from port0,check the received packet on port1.
> +Should receive the packet sent from port0.
> --
> 1.8.3.1


      parent reply	other threads:[~2019-04-03 17:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-26 19:35 Zhe
2019-03-27  6:22 ` Rami Rosen
2019-04-03 17:07 ` Tu, Lijuan [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=8CE3E05A3F976642AAB0F4675D0AD20E0BA5B60B@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=zhe.wan@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).