From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw112202-112199 [PATCH] [v3, 4/4] app/procinfo: support descriptor dump
Date: Wed, 1 Jun 2022 14:29:16 -0400 (EDT) [thread overview]
Message-ID: <20220601182916.E1D6E6D56A@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/112202
_apply patch failure_
Submitter: Min Hu (Connor) <humin29@huawei.com>
Date: Wednesday, June 01 2022 07:49:30
Applied on: CommitID:f62212d39a1b5f1118dabbdfcbae1ac6394291a7
Apply patch set 112202-112199 failed:
Checking patch doc/guides/rel_notes/release_22_07.rst...
Hunk #1 succeeded at 104 (offset -33 lines).
Checking patch lib/ethdev/ethdev_driver.h...
Checking patch lib/ethdev/rte_ethdev.c...
Checking patch lib/ethdev/rte_ethdev.h...
Hunk #1 succeeded at 5452 (offset -4 lines).
Checking patch lib/ethdev/version.map...
error: while searching for:
rte_mtr_color_in_protocol_priority_get;
rte_mtr_color_in_protocol_set;
rte_mtr_meter_vlan_table_update;
};
INTERNAL {
error: patch failed: lib/ethdev/version.map:285
Applied patch doc/guides/rel_notes/release_22_07.rst cleanly.
Applied patch lib/ethdev/ethdev_driver.h cleanly.
Applied patch lib/ethdev/rte_ethdev.c cleanly.
Applied patch lib/ethdev/rte_ethdev.h cleanly.
Applying patch lib/ethdev/version.map with 1 reject...
Rejected hunk #1.
diff a/lib/ethdev/version.map b/lib/ethdev/version.map (rejected hunks)
@@ -285,6 +285,8 @@ EXPERIMENTAL {
rte_mtr_color_in_protocol_priority_get;
rte_mtr_color_in_protocol_set;
rte_mtr_meter_vlan_table_update;
+ rte_eth_rx_hw_desc_dump;
+ rte_eth_tx_hw_desc_dump;
};
INTERNAL {
https://lab.dpdk.org/results/dashboard/patchsets/22389/
UNH-IOL DPDK Community Lab
reply other threads:[~2022-06-01 18:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220601182916.E1D6E6D56A@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
/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).