automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: sergio.gonzalez.monroy@intel.com, test-report@dpdk.org
Subject: [dpdk-test-report] [PatchWork]|ERROR| pw15272-15274 examples/ipsec-secgw: change CBC IV generation
Date: 25 Aug 2016 19:44:56 -0700	[thread overview]
Message-ID: <8dba68$v6thvc@fmsmga002.fm.intel.com> (raw)

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


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

Patchwork ID: 15272-15274
http://www.dpdk.org/dev/patchwork/patch/15274/
Submitter: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
Date: Tue, 23 Aug 2016 17:59:32 +0100
DPDK git baseline: 28d8abaf250c3fb4dcb6416518f4c54b4ae67205

Check patch error:
15272: 
ERROR: return is not a function, parentheses are not required
#230: FILE: examples/ipsec-secgw/ipsec.h:206:
+	return (cop + 1);

total: 1 errors, 0 warnings, 193 lines checked

/home/patchWorkOrg/patches/dpdk-dev-1-3-examples-ipsec-secgw-change-CBC-IV-generation.patch has style problems, please review.

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


patch file error:
15274: 
patching file examples/ipsec-secgw/esp.c patching file examples/ipsec-secgw/ipsec.h Hunk #1 FAILED at 113.
Hunk #2 succeeded at 187 (offset -6 lines).
1 out of 2 hunks FAILED -- saving rejects to file examples/ipsec-secgw/ipsec.h.rej patching file examples/ipsec-secgw/sa.c Hunk #1 FAILED at 63.
Hunk #2 FAILED at 79.
Hunk #3 FAILED at 87.
Hunk #4 FAILED at 255.
Hunk #5 FAILED at 307.
Hunk #6 FAILED at 572.
Hunk #7 FAILED at 593.
7 out of 7 hunks FAILED -- saving rejects to file examples/ipsec-secgw/sa.c.rej

DPDK STV team 

                 reply	other threads:[~2016-08-26  2:44 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='8dba68$v6thvc@fmsmga002.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=sergio.gonzalez.monroy@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).