From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Huisong Li <lihuisong@huawei.com>, zhoumin@loongson.cn
Subject: |WARNING| pw133833-133831 [PATCH v5 1/3] ethdev: introduce maximum Rx buffer size
Date: Fri, 3 Nov 2023 18:07:36 +0800 [thread overview]
Message-ID: <202311031007.3A3A7afB3065006@localhost.localdomain> (raw)
In-Reply-To: <20231103102759.18886-2-lihuisong@huawei.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/133833
_apply patch failure_
Submitter: Huisong Li <lihuisong@huawei.com>
Date: Fri, 3 Nov 2023 18:27:57 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: baa000c5535afb6c4009dd9d70f6c9cc1f2ee853
Apply patch set 133833-133831 failed:
Checking patch doc/guides/rel_notes/release_23_11.rst...
error: while searching for:
a group's miss actions, which are the actions to be performed on packets
that didn't match any of the flow rules in the group.
* **Updated Amazon ena (Elastic Network Adapter) net driver.**
* Upgraded ENA HAL to latest version.
error: patch failed: doc/guides/rel_notes/release_23_11.rst:122
error: doc/guides/rel_notes/release_23_11.rst: patch does not apply
Checking patch lib/ethdev/rte_ethdev.c...
Hunk #1 succeeded at 2145 (offset 33 lines).
Hunk #2 succeeded at 2192 (offset 33 lines).
error: while searching for:
dev_info->min_mtu = RTE_ETHER_MIN_LEN - RTE_ETHER_HDR_LEN -
RTE_ETHER_CRC_LEN;
dev_info->max_mtu = UINT16_MAX;
if (*dev->dev_ops->dev_infos_get == NULL)
return -ENOTSUP;
error: patch failed: lib/ethdev/rte_ethdev.c:3757
error: lib/ethdev/rte_ethdev.c: patch does not apply
Checking patch lib/ethdev/rte_ethdev.h...
Hunk #1 succeeded at 1754 (offset 31 lines).
next parent reply other threads:[~2023-11-03 10:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231103102759.18886-2-lihuisong@huawei.com>
2023-11-03 10:07 ` qemudev [this message]
2023-11-03 10:28 ` |SUCCESS| pw133833 " 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=202311031007.3A3A7afB3065006@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=lihuisong@huawei.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).