automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: roy.fan.zhang@intel.com, test-report@dpdk.org
Subject: [dpdk-test-report] [PatchWork]|ERROR| pw14627-14628 examples/ipsec_secgw: add configuration file support
Date: 08 Jul 2016 01:12:04 -0700	[thread overview]
Message-ID: <4f15c9$tsiigu@fmsmga001.fm.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3557 bytes --]


Test-Label: Intel Niantic on Fedora
Test-Status: ERROR

Patchwork ID: 14627-14628
http://www.dpdk.org/dev/patchwork/patch/14628/
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Thu,  7 Jul 2016 12:31:32 +0100
DPDK git baseline: 737ddf3fb136bcbf6c7228e380741f674cdc56ec

Check patch error:
14627: 
ERROR: trailing whitespace
#95: FILE: doc/guides/sample_app_ug/ipsec_secgw.rst:194:
+*   The ``-f /path/to/config_file`` option enables the application read and $

ERROR: trailing whitespace
#116: FILE: doc/guides/sample_app_ug/ipsec_secgw.rst:227:
+The following sections provide the syntax of configurations to 
+initialize $

ERROR: trailing whitespace
#120: FILE: doc/guides/sample_app_ug/ipsec_secgw.rst:231:
+parsing will result in the appropriate rules being applied to the 
+tables $

ERROR: trailing whitespace
#145: FILE: doc/guides/sample_app_ug/ipsec_secgw.rst:247:
+The parse treats one line in the configuration file as one 
+configuration $

ERROR: trailing whitespace
#146: FILE: doc/guides/sample_app_ug/ipsec_secgw.rst:248:
+item (unless the line concatenation symbol exists). Every configuration 
+$

ERROR: trailing whitespace
#147: FILE: doc/guides/sample_app_ug/ipsec_secgw.rst:249:
+item shall follow the syntax of either SP, SA, or Routing rules 
+specified $

ERROR: trailing whitespace
#619: FILE: doc/guides/sample_app_ug/ipsec_secgw.rst:254:
+ * Comment symbol **#**. Any character from this symbol to the end of $

ERROR: trailing whitespace
#634: FILE: doc/guides/sample_app_ug/ipsec_secgw.rst:269:
+    sp <ip_ver> <dir> esp <action> <priority> <src_ip> <dst_ip> $

ERROR: trailing whitespace
#658: FILE: doc/guides/sample_app_ug/ipsec_secgw.rst:293:
+ $

ERROR: trailing whitespace
#670: FILE: doc/guides/sample_app_ug/ipsec_secgw.rst:305:
+   * *protect <SA_idx>*: the specified traffic is protected by SA rule 
+ $

ERROR: trailing whitespace
#725: FILE: doc/guides/sample_app_ug/ipsec_secgw.rst:360:
+ * Optional: yes, default range of 0 to 0 will be used $

ERROR: trailing whitespace
#745: FILE: doc/guides/sample_app_ug/ipsec_secgw.rst:380:
+All SAs configured with AES-CBC and HMAC-SHA1 share the same values for 
+$

ERROR: trailing whitespace
#796: FILE: doc/guides/sample_app_ug/ipsec_secgw.rst:431:
+ $

ERROR: trailing whitespace
#811: FILE: doc/guides/sample_app_ug/ipsec_secgw.rst:446:
+ * The source IP address. This option is not available when $

ERROR: trailing whitespace
#823: FILE: doc/guides/sample_app_ug/ipsec_secgw.rst:458:
+ * The destination IP address. This option is not available when $

total: 15 errors,0 warnings, 3583 lines checked

NOTE: whitespace errors detected, you may wish to use scripts/cleanpatch or
      scripts/cleanfile
	  
	  /home/patchWorkOrg/patches/dpdk-dev-1-2-examples-ipsec_secgw-add-configuration-file-support.patch has style problems, please review.
	  
	  If any of these errors are false positives, please report them to the maintainer, see CHECKPATCH in MAINTAINERS.
	  
	  14628: 
	  ERROR: trailing whitespace
	  #150: FILE: examples/ipsec-secgw/ep0.cfg:119:
	  +rt ipv6 dst ffff:0000:1111:1111:1111:1111:0000:0000/116 port 3 $
	  
	  total: 1 errors, 0 warnings, 238 lines checked
	  
	  NOTE: whitespace errors detected, you may wish to use scripts/cleanpatch or
	        scripts/cleanfile

/home/patchWorkOrg/patches/dpdk-dev-2-2-examples-ipsec-secgw-add-sample-configuration-files.patch has style problems, please review.

If any of these errors are false positives, please report them to the maintainer, see CHECKPATCH in MAINTAINERS.





DPDK STV team 

                 reply	other threads:[~2016-07-08  8:19 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='4f15c9$tsiigu@fmsmga001.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=roy.fan.zhang@intel.com \
    --cc=test-report@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).