From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: anatoly.burakov@intel.com
Subject: [dpdk-test-report] |FAILURE| pw37694 [PATCH v5 27/70] bus/pci: use memseg walk instead of iteration
Date: 20 Apr 2018 08:49:14 -0700 [thread overview]
Message-ID: <ca5293$1ea9ln@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3875 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/37694
_apply patch file failure_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Mon, 9 Apr 2018 19:00:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fe5abd3150bc1caa8369e743c395c39f53265597
Repo:dpdk-next-crypto, Branch:master, CommitID:8683a65a4f5ee5ce682a48a808a56b9baa190eb4
Repo:dpdk-next-net, Branch:master, CommitID:2d4093beaa47195b54524dc39d4cc13ab6e5d8f0
Repo:dpdk-next-virtio, Branch:master, CommitID:ba3fec3f710a7f0289a14153500a373c4b91671d
Repo:dpdk, Branch:master, CommitID:08efcf533f6a1dc5b12bcf1d5ded83743b8d5cc4
Apply patch file failed:
Repo: dpdk
37694:
patching file drivers/bus/pci/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/bus/pci/Makefile.rej
patching file drivers/bus/pci/linux/pci.c
Hunk #1 FAILED at 116.
1 out of 1 hunk FAILED -- saving rejects to file drivers/bus/pci/linux/pci.c.rej
patching file drivers/bus/pci/meson.build
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/bus/pci/meson.build.rej
Repo: dpdk-next-crypto
37694:
patching file drivers/bus/pci/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/bus/pci/Makefile.rej
patching file drivers/bus/pci/linux/pci.c
Hunk #1 FAILED at 116.
1 out of 1 hunk FAILED -- saving rejects to file drivers/bus/pci/linux/pci.c.rej
patching file drivers/bus/pci/meson.build
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/bus/pci/meson.build.rej
Repo: dpdk-next-net
37694:
patching file drivers/bus/pci/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/bus/pci/Makefile.rej
patching file drivers/bus/pci/linux/pci.c
Hunk #1 FAILED at 116.
1 out of 1 hunk FAILED -- saving rejects to file drivers/bus/pci/linux/pci.c.rej
patching file drivers/bus/pci/meson.build
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/bus/pci/meson.build.rej
Repo: dpdk-next-virtio
37694:
patching file drivers/bus/pci/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/bus/pci/Makefile.rej
patching file drivers/bus/pci/linux/pci.c
Hunk #1 FAILED at 116.
1 out of 1 hunk FAILED -- saving rejects to file drivers/bus/pci/linux/pci.c.rej
patching file drivers/bus/pci/meson.build
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/bus/pci/meson.build.rej
Repo: dpdk-next-eventdev
37694:
patching file drivers/bus/pci/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/bus/pci/Makefile.rej
patching file drivers/bus/pci/linux/pci.c
Hunk #1 FAILED at 116.
1 out of 1 hunk FAILED -- saving rejects to file drivers/bus/pci/linux/pci.c.rej
patching file drivers/bus/pci/meson.build
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/bus/pci/meson.build.rej
DPDK STV team
reply other threads:[~2018-04-20 15:49 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='ca5293$1ea9ln@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=anatoly.burakov@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).