From: sys_stv@intel.com
To: test-report@dpdk.org, aman.deep.singh@intel.com
Subject: [dpdk-test-report] |WARNING| pw(104581) sid(20694) job(PER_PATCH_BUILD9804)[v2] devtools/cocci: added script for ethdev namespace
Date: 22 Nov 2021 10:10:54 -0800 [thread overview]
Message-ID: <311d4e$jbe80i@fmsmga001-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/104581
_apply issues_
Submitter: Aman Singh <aman.deep.singh@intel.com>
Date: 2021-11-22 17:53:22
Reply_mail: 20211122175322.88911-1-aman.deep.singh@intel.com
DPDK git baseline:
Repo:dpdk, CommitID: 0c6e27549c03695f85d949f5195a166b449b419c
* Repo: dpdk
Starting new HTTP connection (1): proxy-prc.intel.com
error: devtools/cocci/namespace_ethdev.cocci: does not exist in index
Applying: devtools/cocci: added script for ethdev namespace
Patch failed at 0001 devtools/cocci: added script for ethdev namespace
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-11-22 18:11 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='311d4e$jbe80i@fmsmga001-auth.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=aman.deep.singh@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).