From: sys_stv@intel.com
To: test-report@dpdk.org,david.hunt@intel.com
Subject: [dpdk-test-report] |ERROR| pw 8363-8368 [dpdk-dev, v2, 6/6] test: add checks for cpu flags on armv8
Date: 31 Oct 2015 07:16:23 -0700 [thread overview]
Message-ID: <f90827$o2vbhd@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
Test-Status: Malformed patch
Submitter: David Hunt <david.hunt@intel.com>
Date: Fri, 30 Oct 2015 11:51:26 +0000
DPDK git baseline: affc455438f4cbd3b14e2d9a24fbc154e22d68d3
Malformed PatchworkID:
http://www.dpdk.org/dev/patchwork/patch/8368/
Error: patching file app/test/test_cpuflags.c
Hunk #2 FAILED at 115.
1 out of 2 hunks FAILED -- saving rejects to file app/test/test_cpuflags.c.rej
http://www.dpdk.org/dev/patchwork/patch/8367/
Error: patching file MAINTAINERS
Hunk #1 FAILED at 124.
1 out of 1 hunk FAILED -- saving rejects to file MAINTAINERS.rej
patching file config/defconfig_arm64-armv8a-linuxapp-gcc
patching file doc/guides/rel_notes/release_2_2.rst
Hunk #1 FAILED at 31.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/rel_notes/release_2_2.rst.rej
patching file mk/arch/arm64/rte.vars.mk
patching file mk/machine/armv8a/rte.vars.mk
DPDK STV team
reply other threads:[~2015-10-31 14:16 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='f90827$o2vbhd@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=david.hunt@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).