From: Nicolas Chautru <nicolas.chautru@intel.com>
To: dev@dpdk.org, gakhil@marvell.com, thomas@monjalon.net,
maxime.coquelin@redhat.com
Cc: trix@redhat.com, ray.kinsella@intel.com,
bruce.richardson@intel.com, hemant.agrawal@nxp.com,
david.marchand@redhat.com, stephen@networkplumber.org,
Nicolas Chautru <nicolas.chautru@intel.com>
Subject: [PATCH v3] doc: announce changes in bbdev related to enum extension
Date: Wed, 8 Jun 2022 17:20:29 -0700 [thread overview]
Message-ID: <1654734030-131230-1-git-send-email-nicolas.chautru@intel.com> (raw)
In-Reply-To: <1647542252-35727-2-git-send-email-nicolas.chautru@intel.com>
v3: being more explicit wrt the list of intended changes for 22.11
v2: indentation fix
Realizing when submitting new bbdev operation in this patch
(https://patchwork.dpdk.org/project/dpdk/list/?series=22111) that this is not workable in practice to extend this API into 22.07 without fundamental ABI breakage even by using existing versionning framework.
Some existing learnings to be applied here to prevent extension being blocked, hence accouncing changes in bbdev intended for 22.11 to make this more future-proof, including dropping max value from enum, as well as deferring extension of the API for FFT operation into DPDK 22.11.
Let me know if any comments or in case this should be captured differently.
Thanks
Nic
Nicolas Chautru (1):
doc: announce changes in bbdev related to enum extension
doc/guides/rel_notes/deprecation.rst | 10 ++++++++++
1 file changed, 10 insertions(+)
--
1.8.3.1
next prev parent reply other threads:[~2022-06-09 0:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 18:37 [PATCH v2] " Nicolas Chautru
2022-03-17 18:37 ` Nicolas Chautru
2022-06-09 0:20 ` Nicolas Chautru [this message]
2022-06-09 0:20 ` [PATCH v3] " Nicolas Chautru
2022-06-09 0:34 ` [PATCH v4] " Nicolas Chautru
2022-06-09 0:34 ` Nicolas Chautru
2022-06-09 5:14 ` Hemant Agrawal
2022-06-09 7:53 ` Maxime Coquelin
2022-06-17 16:13 ` Chautru, Nicolas
2022-06-27 20:47 ` Chautru, Nicolas
2022-06-30 14:52 ` Chautru, Nicolas
2022-07-05 15:45 ` Bruce Richardson
2022-07-17 9:48 ` Thomas Monjalon
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=1654734030-131230-1-git-send-email-nicolas.chautru@intel.com \
--to=nicolas.chautru@intel.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=maxime.coquelin@redhat.com \
--cc=ray.kinsella@intel.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--cc=trix@redhat.com \
/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).