From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |WARNING| pw97017 [PATCH] [v12] eventdev: simplify Rx adapter event vector config
Date: Wed, 18 Aug 2021 01:29:46 -0400 (EDT) [thread overview]
Message-ID: <20210818052946.F1B1689060@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2890 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/97017
_apply patch failure_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Wednesday, August 18 2021 04:59:13
Applied on: CommitID:85b2bc49ce33f9d73a4ebd89483991a95b96b0c8
Apply patch set 97017 failed:
Checking patch app/test-eventdev/test_pipeline_common.c...
Checking patch doc/guides/rel_notes/deprecation.rst...
error: while searching for:
An 8-byte reserved field will be added to the structure ``rte_event_timer`` to
support future extensions.
* eventdev: The structure ``rte_event_eth_rx_adapter_queue_conf`` will be
extended to include ``rte_event_eth_rx_adapter_event_vector_config`` elements
and the function ``rte_event_eth_rx_adapter_queue_event_vector_config`` will
be removed in DPDK 21.11.
An application can enable event vectorization by passing the desired vector
values to the function ``rte_event_eth_rx_adapter_queue_add`` using
the structure ``rte_event_eth_rx_adapter_queue_add``.
* eventdev: Reserved bytes of ``rte_event_crypto_request`` is a space holder
for ``response_info``. Both should be decoupled for better clarity.
New space for ``response_info`` can be made by changing
error: patch failed: doc/guides/rel_notes/deprecation.rst:257
Checking patch lib/eventdev/eventdev_pmd.h...
Checking patch lib/eventdev/rte_event_eth_rx_adapter.c...
Checking patch lib/eventdev/rte_event_eth_rx_adapter.h...
Checking patch lib/eventdev/version.map...
Applied patch app/test-eventdev/test_pipeline_common.c cleanly.
Applying patch doc/guides/rel_notes/deprecation.rst with 1 reject...
Rejected hunk #1.
Applied patch lib/eventdev/eventdev_pmd.h cleanly.
Applied patch lib/eventdev/rte_event_eth_rx_adapter.c cleanly.
Applied patch lib/eventdev/rte_event_eth_rx_adapter.h cleanly.
Applied patch lib/eventdev/version.map cleanly.
diff a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst (rejected hunks)
@@ -257,15 +257,6 @@ Deprecation Notices
An 8-byte reserved field will be added to the structure ``rte_event_timer`` to
support future extensions.
-* eventdev: The structure ``rte_event_eth_rx_adapter_queue_conf`` will be
- extended to include ``rte_event_eth_rx_adapter_event_vector_config`` elements
- and the function ``rte_event_eth_rx_adapter_queue_event_vector_config`` will
- be removed in DPDK 21.11.
-
- An application can enable event vectorization by passing the desired vector
- values to the function ``rte_event_eth_rx_adapter_queue_add`` using
- the structure ``rte_event_eth_rx_adapter_queue_add``.
-
* eventdev: Reserved bytes of ``rte_event_crypto_request`` is a space holder
for ``response_info``. Both should be decoupled for better clarity.
New space for ``response_info`` can be made by changing
https://lab.dpdk.org/results/dashboard/patchsets/18236/
UNH-IOL DPDK Community Lab
reply other threads:[~2021-08-18 5:29 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=20210818052946.F1B1689060@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).