From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw129503 [PATCH] doc: deprecation notice to add callback data to rte_event_fp_ops
Date: Wed, 12 Jul 2023 10:56:11 -0700 (PDT) [thread overview]
Message-ID: <64aee93b.050a0220.326bf.02e3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/129503
_apply patch failure_
Submitter: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Date: Wednesday, July 12 2023 17:30:50
Applied on: CommitID:623dc9364dc6a818799941cc26dc8f70feb2bb24
Apply patch set 129503 failed:
Checking patch doc/guides/rel_notes/deprecation.rst...
error: while searching for:
``rte_cryptodev_get_auth_algo_string``, ``rte_cryptodev_get_aead_algo_string`` and
``rte_cryptodev_asym_get_xform_string`` respectively.
* flow_classify: The flow_classify library and example have no maintainer.
The library is experimental and, as such, it could be removed from DPDK.
Its removal has been postponed to let potential users report interest
error: patch failed: doc/guides/rel_notes/deprecation.rst:133
Applying patch doc/guides/rel_notes/deprecation.rst with 1 reject...
Rejected hunk #1.
hint: Use 'git am --show-current-patch' to see the failed patch
diff a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst (rejected hunks)
@@ -133,6 +133,10 @@ Deprecation Notices
``rte_cryptodev_get_auth_algo_string``, ``rte_cryptodev_get_aead_algo_string`` and
``rte_cryptodev_asym_get_xform_string`` respectively.
+* eventdev: The struct rte_event_fp_ops will be updated with a new element
+ rte_eventdev_port_data to support optional callbacks in DPDK 23.11. This changes
+ the size of rte_event_fp_ops and result in ABI change.
+
* flow_classify: The flow_classify library and example have no maintainer.
The library is experimental and, as such, it could be removed from DPDK.
Its removal has been postponed to let potential users report interest
https://lab.dpdk.org/results/dashboard/patchsets/27059/
UNH-IOL DPDK Community Lab
next reply other threads:[~2023-07-12 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 17:56 dpdklab [this message]
[not found] <20230712173050.599482-1-sivaprasad.tummala@amd.com>
2023-07-12 17:17 ` qemudev
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=64aee93b.050a0220.326bf.02e3SMTPIN_ADDED_MISSING@mx.google.com \
--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).