test suite reviews and discussions
 help / color / mirror / Atom feed
From: Lijuan Tu <lijuan.tu@intel.com>
To: dts@dpdk.org
Cc: Lijuan Tu <lijuan.tu@intel.com>
Subject: [dts] [PATCH 1/4] test_plans/dual_vlan: fix doc build warning
Date: Thu, 31 Jan 2019 21:04:45 +0800	[thread overview]
Message-ID: <1548939888-104647-1-git-send-email-lijuan.tu@intel.com> (raw)

Signed-off-by: Lijuan Tu <lijuan.tu@intel.com>
---
 test_plans/dual_vlan_test_plan.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/test_plans/dual_vlan_test_plan.rst b/test_plans/dual_vlan_test_plan.rst
index 3defc91..e00d7b3 100644
--- a/test_plans/dual_vlan_test_plan.rst
+++ b/test_plans/dual_vlan_test_plan.rst
@@ -153,7 +153,7 @@ Configure the traffic generator to send VLAN packets with the Tag Identifier
  received in port ``B``.
 
 Test Case: Enable/Disable VLAN header stripping
-==============================================
+===============================================
 
 Enable vlan packet forwarding on port ``0`` first::
 
@@ -210,7 +210,7 @@ Configure the traffic generator to send VLAN packets with the Tag Identifier
 Identifier ``1`` can been received in port ``B``.
 
 Test Case: Enable/Disable VLAN header stripping in queue
-=======================================================
+========================================================
 
 Enable vlan packet forwarding on port ``0`` first::
 
-- 
1.8.3.1

             reply	other threads:[~2019-01-31  4:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31 13:04 Lijuan Tu [this message]
2019-01-31 13:04 ` [dts] [PATCH 2/4] test_plans/qos_api: " Lijuan Tu
2019-02-01  5:08   ` Tu, Lijuan
2019-01-31 13:04 ` [dts] [PATCH 3/4] test_plans/vlan_ethertype_config: " Lijuan Tu
2019-02-01  5:08   ` Tu, Lijuan
2019-01-31 13:04 ` [dts] [PATCH 4/4] test_plans/loopback_multi_paths_port_restart_performance: " Lijuan Tu
2019-02-01  5:09   ` Tu, Lijuan
2019-02-01  5:08 ` [dts] [PATCH 1/4] test_plans/dual_vlan: " Tu, Lijuan

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=1548939888-104647-1-git-send-email-lijuan.tu@intel.com \
    --to=lijuan.tu@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).