patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Nicolas Chautru <nicolas.chautru@intel.com>, dev@dpdk.org
Cc: hernan.vargas@intel.com, Vipin.Varghese@amd.com, stable@dpdk.org
Subject: Re: [PATCH v3 2/3] test/bbdev: fix build issue with optional build flag
Date: Wed, 14 Dec 2022 17:16:25 +0100	[thread overview]
Message-ID: <2265eafc-d8f9-5802-678a-5e7c5d4b75f4@redhat.com> (raw)
In-Reply-To: <20221213161855.12970-3-nicolas.chautru@intel.com>



On 12/13/22 17:18, Nicolas Chautru wrote:
> Missing implementation for offload test with FFT.
> Only build when the optional build flag RTE_BBDEV_OFFLOAD_COST
> is set.
> 
> Fixes: 0acdb9866756 ("test/bbdev: add FFT operations cases")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
> ---
>   app/test-bbdev/test_bbdev_perf.c | 82 ++++++++++++++++++++++++++++++++
>   1 file changed, 82 insertions(+)
> 

Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>

Thanks,
Maxime


  reply	other threads:[~2022-12-14 16:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 16:18 [PATCH v3 0/3] test/bbdev: fix build issues " Nicolas Chautru
2022-12-13 16:18 ` [PATCH v3 1/3] test/bbdev: fix build issue " Nicolas Chautru
2022-12-14 16:15   ` Maxime Coquelin
2022-12-13 16:18 ` [PATCH v3 2/3] " Nicolas Chautru
2022-12-14 16:16   ` Maxime Coquelin [this message]
2022-12-13 16:18 ` [PATCH v3 3/3] test/bbdev: explicit check for allocation failure Nicolas Chautru
2022-12-14 16:17   ` Maxime Coquelin
2022-12-14 16:24 ` [PATCH v3 0/3] test/bbdev: fix build issues with optional build flag 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=2265eafc-d8f9-5802-678a-5e7c5d4b75f4@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=Vipin.Varghese@amd.com \
    --cc=dev@dpdk.org \
    --cc=hernan.vargas@intel.com \
    --cc=nicolas.chautru@intel.com \
    --cc=stable@dpdk.org \
    /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).