From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: arybchenko@solarflare.com
Subject: [dpdk-test-report] |FAILURE| pw22996 [PATCH 08/13] net/sfc: initialize port data on attach
Date: 01 Apr 2017 15:59:14 -0700 [thread overview]
Message-ID: <e81775$11lf0te@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3466 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/22996
_apply patch file failure_
Submitter: Andrew Rybchenko <arybchenko@solarflare.com>
Date: Fri, 31 Mar 2017 11:22:18 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:40546b9f72d7367f2ee33c8061896e5c0e92f207
Repo:dpdk-next-crypto, Branch:master, CommitID:3989a0933afab9d339ed9c6de258185d30bb7cb5
Repo:dpdk-next-net, Branch:master, CommitID:a962e4db963d57c1c4c48e46716fc5a63a59542f
Repo:dpdk-next-virtio, Branch:master, CommitID:26f5fd077415b94bb4aacd857d38ae25841f4fe7
Repo:dpdk, Branch:master, CommitID:ba82829fda022e14a938c3a669de0e634626e4c8
Apply patch file failed:
Repo: dpdk
22996:
patching file drivers/net/sfc/sfc.c
Hunk #1 succeeded at 399 (offset -10 lines).
Hunk #2 succeeded at 419 (offset -10 lines).
Hunk #3 succeeded at 443 (offset -10 lines).
Hunk #4 succeeded at 622 (offset 19 lines).
Hunk #5 succeeded at 639 with fuzz 2 (offset 12 lines).
Hunk #6 FAILED at 655.
1 out of 6 hunks FAILED -- saving rejects to file drivers/net/sfc/sfc.c.rej
patching file drivers/net/sfc/sfc.h
Hunk #1 succeeded at 273 (offset -29 lines).
patching file drivers/net/sfc/sfc_port.c
Hunk #1 FAILED at 296.
Hunk #2 succeeded at 248 (offset -126 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/sfc/sfc_port.c.rej
Repo: dpdk-next-crypto
22996:
patching file drivers/net/sfc/sfc.c
Hunk #1 succeeded at 399 (offset -10 lines).
Hunk #2 succeeded at 419 (offset -10 lines).
Hunk #3 succeeded at 443 (offset -10 lines).
Hunk #4 succeeded at 622 (offset 19 lines).
Hunk #5 succeeded at 639 with fuzz 2 (offset 12 lines).
Hunk #6 FAILED at 655.
1 out of 6 hunks FAILED -- saving rejects to file drivers/net/sfc/sfc.c.rej
patching file drivers/net/sfc/sfc.h
Hunk #1 succeeded at 273 (offset -29 lines).
patching file drivers/net/sfc/sfc_port.c
Hunk #1 FAILED at 296.
Hunk #2 succeeded at 248 (offset -126 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/sfc/sfc_port.c.rej
Repo: dpdk-next-virtio
22996:
patching file drivers/net/sfc/sfc.c
Hunk #1 succeeded at 399 (offset -10 lines).
Hunk #2 succeeded at 419 (offset -10 lines).
Hunk #3 succeeded at 443 (offset -10 lines).
Hunk #4 succeeded at 622 (offset 19 lines).
Hunk #5 succeeded at 639 with fuzz 2 (offset 12 lines).
Hunk #6 FAILED at 655.
1 out of 6 hunks FAILED -- saving rejects to file drivers/net/sfc/sfc.c.rej
patching file drivers/net/sfc/sfc.h
Hunk #1 succeeded at 273 (offset -29 lines).
patching file drivers/net/sfc/sfc_port.c
Hunk #1 FAILED at 296.
Hunk #2 succeeded at 248 (offset -126 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/sfc/sfc_port.c.rej
Repo: dpdk-next-eventdev
22996:
patching file drivers/net/sfc/sfc.c
Hunk #1 succeeded at 399 (offset -10 lines).
Hunk #2 succeeded at 419 (offset -10 lines).
Hunk #3 succeeded at 443 (offset -10 lines).
Hunk #4 succeeded at 622 (offset 19 lines).
Hunk #5 succeeded at 639 with fuzz 2 (offset 12 lines).
Hunk #6 FAILED at 655.
1 out of 6 hunks FAILED -- saving rejects to file drivers/net/sfc/sfc.c.rej
patching file drivers/net/sfc/sfc.h
Hunk #1 succeeded at 273 (offset -29 lines).
patching file drivers/net/sfc/sfc_port.c
Hunk #1 FAILED at 296.
Hunk #2 succeeded at 248 (offset -126 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/sfc/sfc_port.c.rej
DPDK STV team
reply other threads:[~2017-04-01 22:59 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='e81775$11lf0te@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=arybchenko@solarflare.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).