From: Stephen Hemminger <stephen@networkplumber.org>
To: Nicolas Chautru <nicolas.chautru@intel.com>
Cc: dev@dpdk.org, maxime.coquelin@redhat.com, trix@redhat.com,
hemant.agrawal@nxp.com, david.marchand@redhat.com,
hernan.vargas@intel.com
Subject: Re: [PATCH v1 1/1] doc: announce change in bbdev api related to operation extension
Date: Thu, 25 May 2023 20:47:22 -0700 [thread overview]
Message-ID: <20230525204722.73635324@hermes.local> (raw)
In-Reply-To: <20230526021132.41413-2-nicolas.chautru@intel.com>
On Fri, 26 May 2023 02:11:32 +0000
Nicolas Chautru <nicolas.chautru@intel.com> wrote:
> +
> +* bbdev: Will extend the API to support the new operation type ``RTE_BBDEV_OP_MLDTS`` as per
> + this `v1 <https://patches.dpdk.org/project/dpdk/list/?series=28192>`. This will also introduce
> + new symbols for ``rte_bbdev_dequeue_mldts_ops``, ``rte_bbdev_enqueue_mldts_ops``,
> + ``rte_bbdev_mldts_op_alloc_bulk`` and ``rte_bbdev_mldts_op_free_bulk``. This will also extend
> + the API related to the FFT operation in ``rte_bbdev_op_fft``.
> --
New symbols do not require a deprecation notice.
Only changes and removal.
next prev parent reply other threads:[~2023-05-26 3:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 2:11 [PATCH v1 0/1] doc: accounce change in bbdev extension Nicolas Chautru
2023-05-26 2:11 ` [PATCH v1 1/1] doc: announce change in bbdev api related to operation extension Nicolas Chautru
2023-05-26 3:47 ` Stephen Hemminger [this message]
2023-06-05 19:07 ` Maxime Coquelin
2023-06-05 20:08 ` Chautru, Nicolas
2023-06-06 9:20 ` David Marchand
2023-06-06 21:01 ` Chautru, Nicolas
2023-06-08 8:47 ` Maxime Coquelin
2023-06-12 20:53 ` Chautru, Nicolas
2023-06-13 8:14 ` Maxime Coquelin
2023-06-13 17:16 ` Chautru, Nicolas
2023-06-13 20:00 ` Maxime Coquelin
2023-06-13 21:22 ` Stephen Hemminger
2023-06-14 18:18 ` Chautru, Nicolas
2023-06-15 7:52 ` Maxime Coquelin
2023-06-15 19:30 ` Chautru, Nicolas
2023-06-16 7:36 ` Maxime Coquelin
2023-06-16 15:48 ` Chautru, Nicolas
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=20230525204722.73635324@hermes.local \
--to=stephen@networkplumber.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=hernan.vargas@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=nicolas.chautru@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.