From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Nicolas Chautru <nicolas.chautru@intel.com>, dev@dpdk.org
Cc: hemant.agrawal@nxp.com, hernan.vargas@intel.com
Subject: Re: [PATCH v1 1/2] doc: update bbdev documentation
Date: Tue, 4 Mar 2025 17:17:14 +0100 [thread overview]
Message-ID: <5f0e77e8-d228-4c69-9a05-c0c88b33ec85@redhat.com> (raw)
In-Reply-To: <20250228165022.480453-2-nicolas.chautru@intel.com>
On 2/28/25 5:50 PM, Nicolas Chautru wrote:
> Correcting the scope of supported bbdev operations.
>
> Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
> ---
> doc/guides/prog_guide/bbdev.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/guides/prog_guide/bbdev.rst b/doc/guides/prog_guide/bbdev.rst
> index e3f356450b..f0fbb0c1c0 100644
> --- a/doc/guides/prog_guide/bbdev.rst
> +++ b/doc/guides/prog_guide/bbdev.rst
> @@ -13,7 +13,7 @@ optimized libraries to appear as virtual bbdev devices.
> The functional scope of the BBDEV library are those functions in relation to
> the 3GPP Layer 1 signal processing (channel coding, modulation, ...).
>
> -The framework currently only supports FEC function.
> +The framework currently supports FEC functions (5G/4G Encoder/Decoder), as well as FFT and MLD-TS.
>
>
> Design Principles
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Thanks,
Maxime
next prev parent reply other threads:[~2025-03-04 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 16:50 [PATCH v1 0/2] bbdev: doc and vector clean up Nicolas Chautru
2025-02-28 16:50 ` [PATCH v1 1/2] doc: update bbdev documentation Nicolas Chautru
2025-03-04 16:17 ` Maxime Coquelin [this message]
2025-02-28 16:50 ` [PATCH v1 2/2] test/bbdev: update to fft test vectors Nicolas Chautru
2025-03-04 16:18 ` Maxime Coquelin
2025-03-04 21:02 ` [PATCH v1 0/2] bbdev: doc and vector clean up Maxime Coquelin
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=5f0e77e8-d228-4c69-9a05-c0c88b33ec85@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=hernan.vargas@intel.com \
--cc=nicolas.chautru@intel.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).