From: Xueming Li <xuemingl@nvidia.com>
Cc: <dev@dpdk.org>, <xuemingl@nvidia.com>, Ray Kinsella <mdr@ashroe.eu>
Subject: [dpdk-dev] [PATCH 1/2] doc: announce eth queue release callback parameter change
Date: Mon, 2 Aug 2021 16:10:54 +0300 [thread overview]
Message-ID: <20210802131056.2683266-1-xuemingl@nvidia.com> (raw)
This patch announces the parameter change of eth_queue_release_t
callback API to eth_dev_ops in DPDK v21.11.
[1] mail list discussion:
https://mails.dpdk.org/archives/dev/2021-July/215654.html
Signed-off-by: Xueming Li <xuemingl@nvidia.com>
---
doc/guides/rel_notes/deprecation.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index d9c0e65921..c38aebe99d 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -131,6 +131,9 @@ Deprecation Notices
consistent with existing outer header checksum status flag naming, which
should help in reducing confusion about its usage.
+* ethdev: queue release callback parameter will be changed to device and queue
+ ID to align with other queue configureation callback.
+
* i40e: As there are both i40evf and iavf pmd, the functions of them are
duplicated. And now more and more advanced features are developed on iavf.
To keep consistent with kernel driver's name
--
2.25.1
next reply other threads:[~2021-08-02 13:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 13:10 Xueming Li [this message]
2021-08-02 13:10 ` [dpdk-dev] [PATCH 2/2] doc: announce eth new offload flag and group field Xueming Li
2021-08-04 8:08 ` Slava Ovsiienko
2021-08-04 12:29 ` Andrew Rybchenko
2021-08-07 13:32 ` Jerin Jacob
2021-08-07 19:15 ` Thomas Monjalon
2021-08-04 12:27 ` [dpdk-dev] [PATCH 1/2] doc: announce eth queue release callback parameter change Andrew Rybchenko
2021-08-04 12:31 ` Xueming(Steven) Li
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=20210802131056.2683266-1-xuemingl@nvidia.com \
--to=xuemingl@nvidia.com \
--cc=dev@dpdk.org \
--cc=mdr@ashroe.eu \
/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).