From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: arybchenko@solarflare.com
Subject: [dpdk-test-report] |FAILURE| pw38570 [PATCH v2 5/8] net/sfc: process RSS settings on Rx configure step
Date: 03 May 2018 04:38:51 -0700 [thread overview]
Message-ID: <0590c7$1idk48@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1473 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38570
_apply patch file failure_
Submitter: Andrew Rybchenko <arybchenko@solarflare.com>
Date: Thu, 19 Apr 2018 17:41:50 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fcde84b5f85b3c1a5d5564299fd49c58ca20370d
Repo:dpdk-next-crypto, Branch:master, CommitID:211992f3b7df5d6d8f1dbefc48bc37a6d5398fbc
Repo:dpdk-next-net, Branch:master, CommitID:60ed72ac5eb5daf57bb19663b0a9aa3a4812487f
Apply patch file failed:
Repo: dpdk
38570:
patching file drivers/net/sfc/sfc_rx.c
Hunk #1 succeeded at 1365 with fuzz 2 (offset 176 lines).
Hunk #2 FAILED at 1451.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/sfc/sfc_rx.c.rej
Repo: dpdk-next-crypto
38570:
patching file drivers/net/sfc/sfc_rx.c
Hunk #1 succeeded at 1365 with fuzz 2 (offset 176 lines).
Hunk #2 FAILED at 1451.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/sfc/sfc_rx.c.rej
Repo: dpdk-next-net
38570:
patching file drivers/net/sfc/sfc_rx.c
Hunk #1 succeeded at 1365 with fuzz 2 (offset 176 lines).
Hunk #2 FAILED at 1451.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/sfc/sfc_rx.c.rej
Repo: dpdk-next-eventdev
38570:
patching file drivers/net/sfc/sfc_rx.c
Hunk #1 succeeded at 1365 with fuzz 2 (offset 176 lines).
Hunk #2 FAILED at 1451.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/sfc/sfc_rx.c.rej
DPDK STV team
reply other threads:[~2018-05-03 11:38 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='0590c7$1idk48@orsmga001.jf.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).