From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw111720 [PATCH] [v3] eal: add bus cleanup to eal cleanup
Date: Tue, 24 May 2022 05:10:30 -0400 (EDT) [thread overview]
Message-ID: <20220524091030.5B8236D4C2@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1736 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/111720
_apply patch failure_
Submitter: Kevin Laatz <kevin.laatz@intel.com>
Date: Tuesday, May 24 2022 09:08:01
Applied on: CommitID:981a025741f80b4036f994ed30b04e757299ab19
Apply patch set 111720 failed:
Checking patch devtools/libabigail.abignore...
error: while searching for:
; Ignore visibility fix of local functions in experimental gpudev library
[suppress_file]
soname_regexp = ^librte_gpudev\.
error: patch failed: devtools/libabigail.abignore:40
Checking patch drivers/bus/pci/pci_common.c...
Checking patch drivers/bus/vdev/vdev.c...
Checking patch lib/eal/common/eal_common_bus.c...
Checking patch lib/eal/include/rte_bus.h...
Checking patch lib/eal/linux/eal.c...
Hunk #1 succeeded at 1266 (offset -2 lines).
Applying patch devtools/libabigail.abignore with 1 reject...
Rejected hunk #1.
Applied patch drivers/bus/pci/pci_common.c cleanly.
Applied patch drivers/bus/vdev/vdev.c cleanly.
Applied patch lib/eal/common/eal_common_bus.c cleanly.
Applied patch lib/eal/include/rte_bus.h cleanly.
Applied patch lib/eal/linux/eal.c cleanly.
diff a/devtools/libabigail.abignore b/devtools/libabigail.abignore (rejected hunks)
@@ -40,3 +40,12 @@
; Ignore visibility fix of local functions in experimental gpudev library
[suppress_file]
soname_regexp = ^librte_gpudev\.
+
+; Ignore field inserted to rte_bus, adding cleanup function
+[suppress_type]
+ name = rte_bus
+ has_data_member_inserted_at = end
+
+; Ignore changes to internally used structs containing rte_bus
+[suppress_type]
+ name = rte_pci_bus, rte_vmbus_bus, rte_vdev_bus
https://lab.dpdk.org/results/dashboard/patchsets/22261/
UNH-IOL DPDK Community Lab
reply other threads:[~2022-05-24 9:10 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=20220524091030.5B8236D4C2@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).