From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Suanming Mou <suanmingm@nvidia.com>, zhoumin@loongson.cn
Subject: |WARNING| pw126229-126232 [RFC PATCH 1/5] crypto/mlx5: add AES-GCM capability
Date: Tue, 18 Apr 2023 17:11:26 +0800 [thread overview]
Message-ID: <202304180911.33I9BQUT3681244@localhost.localdomain> (raw)
In-Reply-To: <20230418092325.2578712-2-suanmingm@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/126229
_apply patch failure_
Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: Tue, 18 Apr 2023 12:23:21 +0300
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 3b3fef9de22af80d173453ab65a80b01ce38cbfd
Apply patch set 126229-126232 failed:
Checking patch doc/guides/nics/mlx5.rst...
error: while searching for:
Set to zero by default.
Supported NICs
--------------
error: patch failed: doc/guides/nics/mlx5.rst:1270
error: doc/guides/nics/mlx5.rst: patch does not apply
Checking patch drivers/common/mlx5/mlx5_devx_cmds.c...
Hunk #1 succeeded at 1110 (offset -87 lines).
Checking patch drivers/common/mlx5/mlx5_devx_cmds.h...
error: while searching for:
struct mlx5_hca_ipsec_reformat_attr reformat_fdb;
};
/* ISO C restricts enumerator values to range of 'int' */
__extension__
enum {
error: patch failed: drivers/common/mlx5/mlx5_devx_cmds.h:153
error: drivers/common/mlx5/mlx5_devx_cmds.h: patch does not apply
Checking patch drivers/common/mlx5/mlx5_prm.h...
Hunk #1 succeeded at 4575 (offset -79 lines).
Hunk #2 succeeded at 4594 (offset -79 lines).
Checking patch drivers/crypto/mlx5/meson.build...
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...
/home/zhoumin/dpdk-ci/tools/../series/27756/126229.patch:483: new blank line at EOF.
+
next parent reply other threads:[~2023-04-18 9:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230418092325.2578712-2-suanmingm@nvidia.com>
2023-04-18 9:11 ` qemudev [this message]
2023-04-18 9:25 ` |SUCCESS| pw126229 " 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=202304180911.33I9BQUT3681244@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).