From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw117631-117637 [PATCH] [v4, 7/7] drivers: mark software PMDs work with IOVA as PA disabled
Date: Fri, 7 Oct 2022 15:48:05 -0400 (EDT) [thread overview]
Message-ID: <20221007194805.7A01B6D509@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/117631
_apply patch failure_
Submitter: Shijith Thotton <sthotton@marvell.com>
Date: Friday, October 07 2022 19:30:29
Applied on: CommitID:e6fde5e04833569efef8f5be6ba12eb64d74b7b6
Apply patch set 117631-117637 failed:
Checking patch doc/guides/rel_notes/release_22_11.rst...
error: while searching for:
* eventdev: Added ``weight`` and ``affinity`` fields
to ``rte_event_queue_conf`` structure.
Known Issues
------------
error: patch failed: doc/guides/rel_notes/release_22_11.rst:269
Checking patch lib/mbuf/rte_mbuf_core.h...
Applying patch doc/guides/rel_notes/release_22_11.rst with 1 reject...
Rejected hunk #1.
Applied patch lib/mbuf/rte_mbuf_core.h cleanly.
diff a/doc/guides/rel_notes/release_22_11.rst b/doc/guides/rel_notes/release_22_11.rst (rejected hunks)
@@ -269,6 +269,9 @@ ABI Changes
* eventdev: Added ``weight`` and ``affinity`` fields
to ``rte_event_queue_conf`` structure.
+* mbuf: Replaced ``buf_iova`` field with ``next`` field and added a new field
+ ``dynfield2`` at its place in second cacheline if ``RTE_IOVA_AS_PA`` is 0.
+
Known Issues
------------
https://lab.dpdk.org/results/dashboard/patchsets/23830/
UNH-IOL DPDK Community Lab
reply other threads:[~2022-10-07 19:48 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=20221007194805.7A01B6D509@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).