From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw(88104) [V2] kni: fix rtnl deadlocks and race conditions v2
Date: 23 Feb 2021 05:06:30 -0800 [thread overview]
Message-ID: <9fae05$c0fb69@orsmga008-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1689 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/88104
_apply issues_
Submitter: Elad Nachman <eladv6@gmail.com>
Date: 2021-02-23 12:05:12
Reply_mail: 20210223120512.29216-1-eladv6@gmail.com
DPDK git baseline:
Repo:dpdk-next-net, CommitID: bd78e24452f181c9d86a3ea3769690e20756139b
Repo:dpdk, CommitID: 51fe32138c860992f228dbf19416ffd3b8e8baf4
* Repo: dpdk-next-net
This will be required in git-pw 2.0
Starting new HTTP connection (1): proxy-shz.intel.com
Starting new HTTP connection (1): proxy-shz.intel.com
error: patch failed: kernel/linux/kni/kni_net.c:110
error: kernel/linux/kni/kni_net.c: patch does not apply
Applying: kni: fix rtnl deadlocks and race conditions v2
Patch failed at 0001 kni: fix rtnl deadlocks and race conditions v2
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
* Repo: dpdk
This will be required in git-pw 2.0
Starting new HTTP connection (1): proxy-shz.intel.com
Starting new HTTP connection (1): proxy-shz.intel.com
error: patch failed: kernel/linux/kni/kni_net.c:110
error: kernel/linux/kni/kni_net.c: patch does not apply
Applying: kni: fix rtnl deadlocks and race conditions v2
Patch failed at 0001 kni: fix rtnl deadlocks and race conditions v2
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
DPDK STV team
reply other threads:[~2021-02-23 13:06 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='9fae05$c0fb69@orsmga008-auth.jf.intel.com' \
--to=sys_stv@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).