From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw65416[v3, 02/15] common/octeontx2: add routine to check if sec capable otx2
Date: 18 Feb 2020 04:13:36 -0800 [thread overview]
Message-ID: <ee68f5$9ce4rq@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/65416
_apply issues_
Submitter: Anoob Joseph <anoobj@marvell.com>
Date: 2020-01-31 10:03:42
Reply_mail: 1580465035-30455-3-git-send-email-anoobj@marvell.com
DPDK git baseline:
Repo:dpdk, CommitID: bc3282125b72ccfe8641f0826955a384f40ca775
*Repo: dpdk
Mellanox mlx4
M: Matan Azrad <matan@mellanox.com>
M: Shahaf Shuler <shahafs@mellanox.com>
error: patch failed: MAINTAINERS:724
error: MAINTAINERS: patch does not apply
Checking patch drivers/common/octeontx2/Makefile...
error: while searching for:
SRCS-y += otx2_irq.c
SRCS-y += otx2_mbox.c
SRCS-y += otx2_common.c
LDLIBS += -lrte_eal
LDLIBS += -lrte_ethdev
error: patch failed: drivers/common/octeontx2/Makefile:31
error: drivers/common/octeontx2/Makefile: patch does not apply
Checking patch drivers/common/octeontx2/meson.build...
error: while searching for:
'otx2_irq.c',
'otx2_mbox.c',
'otx2_common.c',
)
extra_flags = []
error: patch failed: drivers/common/octeontx2/meson.build:6
error: drivers/common/octeontx2/meson.build: patch does not apply
Checking patch drivers/common/octeontx2/otx2_sec_idev.c...
error: drivers/common/octeontx2/otx2_sec_idev.c: already exists in working directory
Checking patch drivers/common/octeontx2/otx2_sec_idev.h...
error: drivers/common/octeontx2/otx2_sec_idev.h: already exists in working directory
DPDK STV team
reply other threads:[~2020-02-18 12:13 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='ee68f5$9ce4rq@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).