From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw111309-111321 [PATCH] [v8, 13/13] vdpa/ifc/base: access correct register for blk device
Date: Wed, 18 May 2022 10:49:52 -0400 (EDT) [thread overview]
Message-ID: <20220518144952.3B94E6D3A7@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/111309
_apply patch failure_
Submitter: Andy Pei <andy.pei@intel.com>
Date: Wednesday, May 18 2022 12:13:55
Applied on: CommitID:18ca4a4ec73a2e28df45a10543b7cdd45f2801dd
Apply patch set 111309-111321 failed:
Checking patch doc/guides/prog_guide/vhost_lib.rst...
Checking patch doc/guides/rel_notes/release_22_07.rst...
error: while searching for:
* ``RTE_EVENT_QUEUE_ATTR_WEIGHT``
* ``RTE_EVENT_QUEUE_ATTR_AFFINITY``
Removed Items
-------------
error: patch failed: doc/guides/rel_notes/release_22_07.rst:104
Checking patch lib/vhost/rte_vhost.h...
Checking patch lib/vhost/socket.c...
Checking patch lib/vhost/vdpa_driver.h...
Checking patch lib/vhost/version.map...
Applied patch doc/guides/prog_guide/vhost_lib.rst cleanly.
Applying patch doc/guides/rel_notes/release_22_07.rst with 1 reject...
Rejected hunk #1.
Applied patch lib/vhost/rte_vhost.h cleanly.
Applied patch lib/vhost/socket.c cleanly.
Applied patch lib/vhost/vdpa_driver.h cleanly.
Applied patch lib/vhost/version.map cleanly.
diff a/doc/guides/rel_notes/release_22_07.rst b/doc/guides/rel_notes/release_22_07.rst (rejected hunks)
@@ -104,6 +104,10 @@ New Features
* ``RTE_EVENT_QUEUE_ATTR_WEIGHT``
* ``RTE_EVENT_QUEUE_ATTR_AFFINITY``
+* **Added vhost API to get the device type of a vDPA device.**
+
+ Added an API which can get the device type of vDPA device.
+
Removed Items
-------------
https://lab.dpdk.org/results/dashboard/patchsets/22167/
UNH-IOL DPDK Community Lab
reply other threads:[~2022-05-18 14:49 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=20220518144952.3B94E6D3A7@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).