From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: arybchenko@solarflare.com
Subject: [dpdk-test-report] |FAILURE| pw32667 [PATCH 10/14] net/sfc: fix incorrect bitwise ORing of L3/L4 packet types
Date: 10 Jan 2018 16:37:30 -0800 [thread overview]
Message-ID: <1f4ae4$ovo85@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/32667
_apply patch file failure_
Submitter: Andrew Rybchenko <arybchenko@solarflare.com>
Date: Sun, 24 Dec 2017 10:46:39 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:d23057095e9beff343d1bd2dd76943192c7070ce
Repo:dpdk-next-crypto, Branch:master, CommitID:34193d50e7ae1cdabbfaa9d26783ac15896438a3
Repo:dpdk-next-net, Branch:master, CommitID:ea6cec076f0a97be33b11d9b6fe1d7abe90319b3
Repo:dpdk-next-virtio, Branch:master, CommitID:e9e957b8725bffb3d2ffb18467ffab91e3f2fa2e
Repo:dpdk, Branch:master, CommitID:f06125c07d6203a84e9b242c62d6a8e532a5c51d
Apply patch file failed:
Repo: dpdk-next-net
32667:
patching file drivers/net/sfc/sfc_ef10_rx.c
Hunk #1 FAILED at 286.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/sfc/sfc_ef10_rx.c.rej
DPDK STV team
reply other threads:[~2018-01-11 0:37 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='1f4ae4$ovo85@orsmga002.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).