From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw50646[2/2] kernel/windows: set FILE_AUTOGENERATED_DEVICE_NAME to true so that SDDL string can be set successfully. Fixes: 9087d5ff8375 ("doc: change the Windows UIO driver's default security descriptor to admin only") Cc: haramakr@microsoft.com
Date: 28 Feb 2019 08:34:56 -0800 [thread overview]
Message-ID: <e75792$47qf1v@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/50646
_apply issues_
Submitter: Martin Birks <martin.birks@activfinancial.com>
Date: 2019-02-28 15:38:03
Reply_mail: 20190228153803.22756-3-martin.birks@activfinancial.com
DPDK git baseline:
Repo:dpdk-master, CommitID: 8d47a753b7cb05e0ef62360324c6a28505038d09
Repo:dpdk-next-eventdev, CommitID: 41d8285bdf0a7cd8f0d4f1b306e0ced9556081ac
Repo:dpdk-next-net, CommitID: b7e73b4f9a4a72724fde50f2fbefef5afb7aac1d
Repo:dpdk-next-crypto, CommitID: c652031bf46709a3a9e7bda21722ad7627f7944e
Repo:dpdk-next-virtio, CommitID: 4f102e62abeb2af8be8d42c71f87b5d33f0dda38
*Repo: dpdk-master
Checking patch kernel/windows/netuio/netuio_dev.c...
error: kernel/windows/netuio/netuio_dev.c: No such file or directory
*Repo: dpdk-next-eventdev
Checking patch kernel/windows/netuio/netuio_dev.c...
error: kernel/windows/netuio/netuio_dev.c: No such file or directory
*Repo: dpdk-next-net
Checking patch kernel/windows/netuio/netuio_dev.c...
error: kernel/windows/netuio/netuio_dev.c: No such file or directory
*Repo: dpdk-next-crypto
Checking patch kernel/windows/netuio/netuio_dev.c...
error: kernel/windows/netuio/netuio_dev.c: No such file or directory
*Repo: dpdk-next-virtio
Checking patch kernel/windows/netuio/netuio_dev.c...
error: kernel/windows/netuio/netuio_dev.c: No such file or directory
DPDK STV team
reply other threads:[~2019-02-28 16:35 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$47qf1v@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).