From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Bing Zhao <bingz@nvidia.com>, zhoumin@loongson.cn
Subject: |WARNING| pw129159 [PATCH v2] net/mlx5: fix the error in VLAN actions creation
Date: Fri, 30 Jun 2023 18:45:12 +0800 [thread overview]
Message-ID: <202306301045.35UAjCAk1642680@localhost.localdomain> (raw)
In-Reply-To: <20230630105129.434516-1-bingz@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/129159
_apply patch failure_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Fri, 30 Jun 2023 13:51:29 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: f95b4da66528b97e7fa44f3503a34c193b2efb44
Apply patch set 129159 failed:
Checking patch drivers/net/mlx5/mlx5_flow_hw.c...
Hunk #1 succeeded at 7078 (offset -47 lines).
error: while searching for:
}
}
ret = flow_hw_create_vlan(dev);
if (ret)
goto err;
if (_queue_attr)
mlx5_free(_queue_attr);
if (port_attr->flags & RTE_FLOW_PORT_FLAG_STRICT_QUEUE)
error: patch failed: drivers/net/mlx5/mlx5_flow_hw.c:7920
error: drivers/net/mlx5/mlx5_flow_hw.c: patch does not apply
next parent reply other threads:[~2023-06-30 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230630105129.434516-1-bingz@nvidia.com>
2023-06-30 10:45 ` qemudev [this message]
2023-06-30 10:53 ` 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=202306301045.35UAjCAk1642680@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=bingz@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).