DPDK patches and discussions
 help / color / mirror / Atom feed
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 0/2] bbdev: doc and vector clean up
Date: Tue, 4 Mar 2025 22:02:49 +0100	[thread overview]
Message-ID: <28ff64d6-8a6a-4992-83c5-25c43264e662@redhat.com> (raw)
In-Reply-To: <20250228165022.480453-1-nicolas.chautru@intel.com>



On 2/28/25 5:50 PM, Nicolas Chautru wrote:
> Minor changes to clean up the documentation for bbdev programming guide
> and updating vectors to avoid false alarms when using different
> windowing configuration assumption by users.
> 
> Nicolas Chautru (2):
>    doc: update bbdev documentation
>    test/bbdev: update to fft test vectors
> 
>   app/test-bbdev/test_vectors/fft_9.data      | 870 --------------------
>   app/test-bbdev/test_vectors/fft_byp_28.data |  48 +-
>   doc/guides/prog_guide/bbdev.rst             |   2 +-
>   3 files changed, 25 insertions(+), 895 deletions(-)
>   delete mode 100644 app/test-bbdev/test_vectors/fft_9.data
> 

Series applied to next-baseband/for-main.
I added the fixes tag on patch 2 as discussed off-list.

Thanks,
Maxime


      parent reply	other threads:[~2025-03-04 21:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 16:50 Nicolas Chautru
2025-02-28 16:50 ` [PATCH v1 1/2] doc: update bbdev documentation Nicolas Chautru
2025-03-04 16:17   ` Maxime Coquelin
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 ` Maxime Coquelin [this message]

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=28ff64d6-8a6a-4992-83c5-25c43264e662@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).