From: sys_stv@intel.com
To: krytarowski@caviumnetworks.com, test-report@dpdk.org
Subject: [dpdk-test-report] [PatchWork]|ERROR| pw15423-15435 net/thunderx: cleanup the driver before adding new features
Date: 02 Sep 2016 00:25:41 -0700 [thread overview]
Message-ID: <4f15c9$uql3r3@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork ID: 15423-15435
http://www.dpdk.org/dev/patchwork/patch/15435/
Submitter: Kamil Rytarowski <krytarowski@caviumnetworks.com>
Date: Fri, 26 Aug 2016 18:53:56 +0200
DPDK git baseline: e22856313fff2db12d8e132dad446bbf74cf29a5
Check patch error:
15435:
ERROR: trailing whitespace
#94: FILE: doc/guides/nics/thunderx.rst:375:
+ $
ERROR: trailing whitespace
#98: FILE: doc/guides/nics/thunderx.rst:379:
+ $
ERROR: trailing whitespace
#122: FILE: doc/guides/nics/thunderx.rst:403:
+ $
total: 3 errors, 0 warnings, 122 lines checked
NOTE: whitespace errors detected, you may wish to use scripts/cleanpatch or
scripts/cleanfile
/home/patchWorkOrg/patches/dpdk-dev-13-13-net-thunderx-document-secondary-queue-set-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.
patch file error:
15423:
patching file drivers/net/thunderx/base/nicvf_hw.c
Hunk #1 FAILED at 141.
Hunk #2 succeeded at 494 (offset -3 lines).
Hunk #3 succeeded at 511 (offset -3 lines).
1 out of 3 hunks FAILED -- saving rejects to file drivers/net/thunderx/base/nicvf_hw.c.rej
patching file drivers/net/thunderx/base/nicvf_hw.h
patching file drivers/net/thunderx/nicvf_ethdev.c
Hunk #4 succeeded at 1204 (offset -5 lines).
Hunk #5 succeeded at 1347 (offset -5 lines).
Hunk #6 succeeded at 1714 (offset -5 lines).
DPDK STV team
reply other threads:[~2016-09-02 7:25 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$uql3r3@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=krytarowski@caviumnetworks.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).