From: sys_stv@intel.com
To: yulong.pei@intel.com, test-report@dpdk.org
Subject: [dpdk-test-report] [PatchWork]|ERROR| pw13199 eal: fix allocating all free hugepages
Date: 05 Jun 2016 23:17:54 -0700 [thread overview]
Message-ID: <9c8bee$t834lf@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork ID: 13199
http://www.dpdk.org/dev/patchwork/patch/13199/
Submitter: "Pei, Yulong" <yulong.pei@intel.com>
Date: Mon, 6 Jun 2016 02:49:26 +0000
DPDK git baseline: f243d9b04b4bf17d7ccdae179fa43b04d8a87317
Check patch error:
13199:
ERROR: open brace '{' following function declarations go on the next line
#339: FILE: lib/librte_eal/linuxapp/eal/eal_memory.c:316:
+static void huge_sigbus_handler(int signo __rte_unused) {
ERROR: trailing whitespace
#343: FILE: lib/librte_eal/linuxapp/eal/eal_memory.c:320:
+/* Put setjmp into a wrap method to avoid compiling error. Any $
ERROR: trailing whitespace
#345: FILE: lib/librte_eal/linuxapp/eal/eal_memory.c:322:
+ * non-static local variable in the stack frame calling sigsetjmp might
+ $
total: 3 errors, 0 warnings, 209 lines checked
NOTE: whitespace errors detected, you may wish to use scripts/cleanpatch or
scripts/cleanfile
/home/patchWorkOrg/patches/dpdk-dev-v5-eal-fix-allocating-all-free-hugepages.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:
13199:
patching file lib/librte_eal/linuxapp/eal/eal.c Hunk #1 FAILED at 465.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/linuxapp/eal/eal.c.rej
patching file lib/librte_eal/linuxapp/eal/eal_memory.c
DPDK STV team
reply other threads:[~2016-06-06 6:17 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='9c8bee$t834lf@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=yulong.pei@intel.com \
/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).