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 0/3] test/bbdev: fix build issues with optional build flag
Date: Wed, 14 Dec 2022 17:24:07 +0100 [thread overview]
Message-ID: <0725e1de-03b7-7de5-802b-61486f0fcb34@redhat.com> (raw)
In-Reply-To: <20221213161855.12970-1-nicolas.chautru@intel.com>
On 12/13/22 17:18, Nicolas Chautru wrote:
> v3: add more Fixes tag for missing error check commit
> v2: add check in offload test function for error during allocation
> suggested by Maxime.
> Fixing compilation errors in bbdev-test application on rc4
> when the optional flag RTE_BBDEV_OFFLOAD_COST is set manually.
> This was raised by Vipin.
>
> Nicolas Chautru (3):
> test/bbdev: fix build issue with optional build flag
> test/bbdev: fix build issue with optional build flag
> test/bbdev: explicit check for allocation failure
>
> app/test-bbdev/test_bbdev_perf.c | 93 ++++++++++++++++++++++++++++++--
> 1 file changed, 89 insertions(+), 4 deletions(-)
>
Applied to dpdk-next-baseband/for-main.
Thanks,
Maxime
prev parent reply other threads:[~2022-12-14 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 16:18 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
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 ` 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=0725e1de-03b7-7de5-802b-61486f0fcb34@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).