From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw50904[3/6] net/mlx5: add control of excessive memory pinning by kernel
Date: 07 Mar 2019 02:03:37 -0800 [thread overview]
Message-ID: <e75792$512j33@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/50904
_apply issues_
Submitter: Yongseok Koh <yskoh@mellanox.com>
Date: 2019-03-07 07:41:48
Reply_mail: 20190307074151.18815-4-yskoh@mellanox.com
DPDK git baseline:
Repo:dpdk-master, CommitID: e892fa595e19b5cce315045444b3b7e31130ef19
Repo:dpdk-next-eventdev, CommitID: 41d8285bdf0a7cd8f0d4f1b306e0ced9556081ac
Repo:dpdk-next-net, CommitID: 48d02a65290b48bdd60ef4d45ba16eb3b5e27e9b
Repo:dpdk-next-crypto, CommitID: 0db1459f6bb820d3dd9dcd2a74bc126ae276eac1
Repo:dpdk-next-virtio, CommitID: 4f102e62abeb2af8be8d42c71f87b5d33f0dda38
Apply patchset failed, the failed patch is: http://dpdk.org/patch/50903
DPDK STV team
reply other threads:[~2019-03-07 10:03 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='e75792$512j33@orsmga001.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).