test suite reviews and discussions
 help / color / mirror / Atom feed
From: Peng Yuan <yuan.peng@intel.com>
To: dts@dpdk.org
Cc: Peng Yuan <yuan.peng@intel.com>
Subject: [dts] [PATCH]test_plans: add dump_devargs case
Date: Tue,  4 Jun 2019 17:53:58 +0800	[thread overview]
Message-ID: <1559642038-135357-1-git-send-email-yuan.peng@intel.com> (raw)

Remove the dump_log_history, add dump_devargs case.

Signed-off-by: Peng Yuan <yuan.peng@intel.com>

diff --git a/test_plans/unit_tests_dump_test_plan.rst b/test_plans/unit_tests_dump_test_plan.rst
index cc34eed..39d77eb 100644
--- a/test_plans/unit_tests_dump_test_plan.rst
+++ b/test_plans/unit_tests_dump_test_plan.rst
@@ -30,14 +30,14 @@
    ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
    OF THE POSSIBILITY OF SUCH DAMAGE.
 
-============================
-Unit Tests: Dump Log History
-============================
+========================
+Unit Tests: Dump Devargs
+========================
 
-This is the test plan for dump history log of Intel® DPDK .
+This is the test plan for dump device arguments of Intel® DPDK.
 
-This section explains how to run the unit tests for dump history log. The test
-can be launched independently using the command line interface.
+This section explains how to run the unit tests for dump device arguments.
+The test can be launched independently using the command line interface.
 This test is implemented as a linuxapp environment application.
 
 The complete test suite is launched automatically using a python-expect
@@ -48,10 +48,11 @@ stdout.
 The steps to run the unit test manually are as follow::
 
   # make -C ./app/test/
-  # ./app/test/test -n 1 -c ffff
-  RTE>> dump_log_history
+  # ./app/test/test -n 1 -c ffff -w|-b pci_address
+  RTE>> dump_devargs
 
-The final output of the test will be the initial log of DPDK.
+The final output of the test will be the pci address of white list
+or black list.
 
 =====================
 Unit Tests: Dump Ring
-- 
2.7.4


                 reply	other threads:[~2019-06-04  9:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1559642038-135357-1-git-send-email-yuan.peng@intel.com \
    --to=yuan.peng@intel.com \
    --cc=dts@dpdk.org \
    /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).