From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Gnanesh <gpalanethra@marvell.com>, zhoumin@loongson.cn
Subject: |WARNING| pw147854 [PATCH 1/1] Cn10K crypto Tests: Added Marvell Cn10K specific crypto Tests to TestCryptoPerfCryptodevPerf
Date: Thu, 31 Oct 2024 22:30:21 +0800 [thread overview]
Message-ID: <202410311430.49VEULds4166385@localhost.localdomain> (raw)
In-Reply-To: <20241031104322.3169217-1-gpalanethra@marvell.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/147854
_apply patch failure_
Submitter: Gnanesh <gpalanethra@marvell.com>
Date: Thu, 31 Oct 2024 16:13:22 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 2a682d65f8dbe1e8be9cc2425095827e18c700e3
Apply patch set 147854 failed:
Checking patch conf/crypto_perf_cryptodev_perf.cfg...
error: conf/crypto_perf_cryptodev_perf.cfg: No such file or directory
Checking patch framework/crb.py...
error: framework/crb.py: No such file or directory
Checking patch framework/settings.py...
error: framework/settings.py: No such file or directory
Checking patch framework/ssh_pexpect.py...
error: framework/ssh_pexpect.py: No such file or directory
Checking patch nics/net_device.py...
error: nics/net_device.py: No such file or directory
Checking patch tests/TestSuite_crypto_perf_cryptodev_perf.py...
error: tests/TestSuite_crypto_perf_cryptodev_perf.py: No such file or directory
Checking patch tests/cryptodev_common.py...
error: tests/cryptodev_common.py: No such file or directory
next parent reply other threads:[~2024-10-31 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241031104322.3169217-1-gpalanethra@marvell.com>
2024-10-31 14:30 ` qemudev [this message]
2024-10-31 15:04 ` checkpatch
2024-10-31 15:46 ` |WARNING| pw147854 [PATCH] [1/1] " dpdklab
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=202410311430.49VEULds4166385@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=gpalanethra@marvell.com \
--cc=test-report@dpdk.org \
--cc=zhoumin@loongson.cn \
/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).