automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Suanming Mou <suanmingm@nvidia.com>, zhoumin@loongson.cn
Subject: |WARNING| pw127522-127530 [PATCH v2 1/9] common/mlx5: export memory region lookup by address
Date: Fri, 26 May 2023 11:11:39 +0800	[thread overview]
Message-ID: <202305260311.34Q3Bd16744932@localhost.localdomain> (raw)
In-Reply-To: <20230526031422.913377-2-suanmingm@nvidia.com>

Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/127522

_apply patch failure_

Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: Fri, 26 May 2023 06:14:13 +0300
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: c9df59bcc9bec67783de98486879594e52bdc418

Apply patch set 127522-127530 failed:

Checking patch doc/guides/cryptodevs/mlx5.rst...
Checking patch doc/guides/rel_notes/release_23_07.rst...
error: while searching for:
  * Added support for multi-packet RQ on Windows.
  * Added support for CQE compression on Windows.
  * Added support for enhanced multi-packet write on Windows.

* **Added flow matching of tx queue.**


error: patch failed: doc/guides/rel_notes/release_23_07.rst:29
error: doc/guides/rel_notes/release_23_07.rst: patch does not apply
Checking patch drivers/crypto/mlx5/mlx5_crypto.c...
Checking patch drivers/crypto/mlx5/mlx5_crypto.h...
Checking patch drivers/crypto/mlx5/mlx5_crypto_gcm.c...


       reply	other threads:[~2023-05-26  3:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230526031422.913377-2-suanmingm@nvidia.com>
2023-05-26  3:11 ` qemudev [this message]
2023-05-26  3:16 ` |SUCCESS| pw127522 " checkpatch

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=202305260311.34Q3Bd16744932@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=suanmingm@nvidia.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).