automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw112478-112484 [PATCH] [v3, 7/7] net/ark: add PMD support for devices as virtual functions
Date: Tue,  7 Jun 2022 12:09:12 -0400 (EDT)	[thread overview]
Message-ID: <20220607160912.AA3AE6D56A@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]

Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/112478

_apply patch failure_

Submitter: Ed Czeck <ed.czeck@atomicrules.com>
Date: Tuesday, June 07 2022 15:49:17 
Applied on: CommitID:bebbf0721943ad2c6632026c4235e48d5f37b88f
Apply patch set 112478-112484 failed:

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 drivers/net/ark/ark_ethdev.c...
Checking patch drivers/net/ark/ark_global.h...
Applying patch doc/guides/rel_notes/release_22_07.rst with 1 reject...
Rejected hunk #1.
Applied patch drivers/net/ark/ark_ethdev.c cleanly.
Applied patch drivers/net/ark/ark_global.h 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,11 @@ New Features
   * ``RTE_EVENT_QUEUE_ATTR_WEIGHT``
   * ``RTE_EVENT_QUEUE_ATTR_AFFINITY``
 
+* **Updated Atomic Rules' Arkville PMD.**
+
+  Added support for Atomic Rules PCI device IDs ``0x101a, 0x101b, 0x101c``.
+
+  Added PMD support for virtual functions and vfio_pci driver.
 
 Removed Items
 -------------

https://lab.dpdk.org/results/dashboard/patchsets/22489/

UNH-IOL DPDK Community Lab

                 reply	other threads:[~2022-06-07 16:09 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=20220607160912.AA3AE6D56A@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).