From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Amit Prakash Shukla <amitprakashs@marvell.com>, zhoumin@loongson.cn
Subject: |WARNING| pw138465 [PATCH] doc: add dma perf feature details
Date: Tue, 19 Mar 2024 01:55:53 +0800 [thread overview]
Message-ID: <202403181755.42IHtrxV2709188@localhost.localdomain> (raw)
In-Reply-To: <20240318181730.2725829-1-amitprakashs@marvell.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/138465
_apply patch failure_
Submitter: Amit Prakash Shukla <amitprakashs@marvell.com>
Date: Mon, 18 Mar 2024 23:47:30 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
Apply patch set 138465 failed:
Checking patch doc/guides/tools/dmaperf.rst...
error: while searching for:
Configuration Parameters
~~~~~~~~~~~~~~~~~~~~~~~~
``type``
The type of the test.
Currently supported types are ``DMA_MEM_COPY`` and ``CPU_MEM_COPY``.
``mem_size``
The size of the memory footprint.
error: patch failed: doc/guides/tools/dmaperf.rst:69
error: doc/guides/tools/dmaperf.rst: patch does not apply
next parent reply other threads:[~2024-03-18 18:20 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240318181730.2725829-1-amitprakashs@marvell.com>
2024-03-18 17:55 ` qemudev [this message]
2024-03-18 18:18 ` |SUCCESS| " checkpatch
2024-03-18 19:08 ` dpdklab
2024-03-18 19:09 ` dpdklab
2024-03-18 19:09 ` dpdklab
2024-03-18 19:10 ` dpdklab
2024-03-18 19:11 ` dpdklab
2024-03-18 19:16 ` dpdklab
2024-03-18 19:16 ` dpdklab
2024-03-18 19:16 ` dpdklab
2024-03-18 19:16 ` dpdklab
2024-03-18 19:17 ` dpdklab
2024-03-18 19:17 ` dpdklab
2024-03-18 19:17 ` dpdklab
2024-03-18 19:17 ` dpdklab
2024-03-18 19:18 ` dpdklab
2024-03-18 19:18 ` dpdklab
2024-03-18 19:18 ` dpdklab
2024-03-18 19:18 ` dpdklab
2024-03-18 19:19 ` dpdklab
2024-03-18 19:19 ` dpdklab
2024-03-18 19:19 ` dpdklab
2024-03-18 19:19 ` dpdklab
2024-03-18 19:20 ` dpdklab
2024-03-18 19:20 ` dpdklab
2024-03-18 19:20 ` dpdklab
2024-03-18 19:22 ` dpdklab
2024-03-18 19:23 ` dpdklab
2024-03-18 19:23 ` dpdklab
2024-03-18 19:23 ` dpdklab
2024-03-18 19:23 ` dpdklab
2024-03-18 19:23 ` dpdklab
2024-03-18 19:23 ` dpdklab
2024-03-18 19:23 ` dpdklab
2024-03-18 19:24 ` dpdklab
2024-03-18 19:24 ` dpdklab
2024-03-18 19:24 ` dpdklab
2024-03-18 19:24 ` dpdklab
2024-03-18 19:24 ` dpdklab
2024-03-18 19:24 ` dpdklab
2024-03-18 19:24 ` dpdklab
2024-03-18 19:25 ` dpdklab
2024-03-18 19:25 ` dpdklab
2024-03-18 19:25 ` dpdklab
2024-03-18 19:25 ` dpdklab
2024-03-18 19:25 ` dpdklab
2024-03-18 19:25 ` dpdklab
2024-03-18 19:25 ` dpdklab
2024-03-18 19:25 ` dpdklab
2024-03-18 19:26 ` dpdklab
2024-03-18 19:26 ` dpdklab
2024-03-18 19:26 ` dpdklab
2024-03-18 19:26 ` dpdklab
2024-03-18 19:26 ` dpdklab
2024-03-18 19:28 ` dpdklab
2024-03-18 19:28 ` dpdklab
2024-03-18 19:28 ` dpdklab
2024-03-18 19:28 ` dpdklab
2024-03-18 19:29 ` dpdklab
2024-03-18 19:29 ` dpdklab
2024-03-18 19:29 ` dpdklab
2024-03-18 19:29 ` dpdklab
2024-03-18 19:30 ` dpdklab
2024-03-18 19:32 ` dpdklab
2024-03-18 19:32 ` dpdklab
2024-03-18 19:32 ` dpdklab
2024-03-18 19:32 ` dpdklab
2024-03-18 19:33 ` dpdklab
2024-03-18 19:33 ` dpdklab
2024-03-18 19:33 ` dpdklab
2024-03-18 19:33 ` dpdklab
2024-03-18 19:34 ` dpdklab
2024-03-18 19:36 ` dpdklab
2024-03-18 19:38 ` dpdklab
2024-03-18 20:00 ` dpdklab
2024-03-18 20:43 ` dpdklab
2024-03-20 17:05 ` dpdklab
2024-03-20 17:39 ` 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=202403181755.42IHtrxV2709188@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=amitprakashs@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).