From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |WARNING| pw98736 [PATCH] eal: promote rte_mcfg_get_single_file_segment to stable ABI
Date: Mon, 13 Sep 2021 05:13:11 -0400 (EDT) [thread overview]
Message-ID: <20210913091311.492B288E6A@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1785 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/98736
_apply patch failure_
Submitter: Jakub Grajciar -X (jgrajcia - PANTHEON TECH SRO at Cisco) <jgrajcia@cisco.com>
Date: Monday, September 13 2021 08:44:13
Applied on: CommitID:962bbb0b7f56ab982d6337c9bae05e1b105f8bdd
Apply patch set 98736 failed:
Checking patch doc/guides/rel_notes/release_21_11.rst...
Hunk #1 succeeded at 117 (offset 10 lines).
Checking patch lib/eal/include/rte_eal_memconfig.h...
Checking patch lib/eal/version.map...
error: while searching for:
rte_malloc_socket;
rte_malloc_validate;
rte_malloc_virt2iova;
rte_mcfg_mem_read_lock;
rte_mcfg_mem_read_unlock;
rte_mcfg_mem_write_lock;
error: patch failed: lib/eal/version.map:121
error: while searching for:
rte_mcfg_timer_unlock;
rte_rand_max; # WINDOWS_NO_EXPORT
# added in 19.11
rte_mcfg_get_single_file_segments;
# added in 20.02
rte_thread_is_intr;
error: patch failed: lib/eal/version.map:328
Applied patch doc/guides/rel_notes/release_21_11.rst cleanly.
Applied patch lib/eal/include/rte_eal_memconfig.h cleanly.
Applying patch lib/eal/version.map with 2 rejects...
Rejected hunk #1.
Rejected hunk #2.
diff a/lib/eal/version.map b/lib/eal/version.map (rejected hunks)
@@ -121,6 +121,7 @@ DPDK_22 {
rte_malloc_socket;
rte_malloc_validate;
rte_malloc_virt2iova;
+ rte_mcfg_get_single_file_segments;
rte_mcfg_mem_read_lock;
rte_mcfg_mem_read_unlock;
rte_mcfg_mem_write_lock;
@@ -328,9 +329,6 @@ EXPERIMENTAL {
rte_mcfg_timer_unlock;
rte_rand_max; # WINDOWS_NO_EXPORT
- # added in 19.11
- rte_mcfg_get_single_file_segments;
-
# added in 20.02
rte_thread_is_intr;
https://lab.dpdk.org/results/dashboard/patchsets/18703/
UNH-IOL DPDK Community Lab
next reply other threads:[~2021-09-13 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 9:13 dpdklab [this message]
[not found] <CY4PR1101MB21025AB8F174E665B6D53EFADFD99@CY4PR1101MB2102.namprd11.prod.outlook.com>
2021-09-13 8:45 ` 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=20210913091311.492B288E6A@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).