patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Xueming Li <xuemingl@nvidia.com>
To: "Jiang, YuX" <yux.jiang@intel.com>,
	Brian Dooley <brian.dooley@intel.com>,
	 Akhil Goyal <gakhil@marvell.com>,
	Fan Zhang <fanzhang.oss@gmail.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH] test/crypto: fix callback setup tests
Date: Tue, 22 Apr 2025 08:05:19 +0000	[thread overview]
Message-ID: <CH3PR12MB8658C018CD477C641D083964A1BB2@CH3PR12MB8658.namprd12.prod.outlook.com> (raw)
In-Reply-To: <IA0PR11MB8336504939A78A28D0056F6BFEBB2@IA0PR11MB8336.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2292 bytes --]

Hi Jiang,

Thanks for reminding, patch included and created new tag v23.11.4-rc5. Please check.

Thanks,
Xueming Li
________________________________
From: Jiang, YuX <yux.jiang@intel.com>
Sent: Tuesday, April 22, 2025 2:14 PM
To: Xueming Li <xuemingl@nvidia.com>; Brian Dooley <brian.dooley@intel.com>; Akhil Goyal <gakhil@marvell.com>; Fan Zhang <fanzhang.oss@gmail.com>
Cc: stable@dpdk.org <stable@dpdk.org>; Dooley, Brian <brian.dooley@intel.com>
Subject: RE: [PATCH] test/crypto: fix callback setup tests

Hi Xueming,
Can you pls make the patch queue to stable release 23.11.x?

> -----Original Message-----
> From: Brian Dooley <brian.dooley@intel.com>
> Sent: Thursday, November 7, 2024 10:09 PM
> To: Akhil Goyal <gakhil@marvell.com>; Fan Zhang <fanzhang.oss@gmail.com>
> Cc: stable@dpdk.org; Dooley, Brian <brian.dooley@intel.com>
> Subject: [PATCH] test/crypto: fix callback setup tests
>
> The test_deq_callback_setup and test_enq_callback_setup tests are asserting
> the incorrect case and need to be reversed to reflect correct callbacks being
> called.
>
> Fixes: 4fe42b5bd587 ("test/crypto: fix enqueue/dequeue callback case")
>
> Signed-off-by: Brian Dooley <brian.dooley@intel.com>
> ---
>  app/test/test_cryptodev.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/app/test/test_cryptodev.c b/app/test/test_cryptodev.c index
> 6cd38aefae..005d3a87f9 100644
> --- a/app/test/test_cryptodev.c
> +++ b/app/test/test_cryptodev.c
> @@ -13727,7 +13727,7 @@ test_enq_callback_setup(void)
>                        "qp %u on cryptodev %u",
>                        qp_id, ts_params->valid_devs[0]);
>
> -     TEST_ASSERT(deq_cb_called == true, "Crypto dequeue callback not
> called");
> +     TEST_ASSERT(enq_cb_called == true, "Crypto enqueue callback not
> +called");
>
>        return TEST_SUCCESS;
>  }
> @@ -13848,7 +13848,7 @@ test_deq_callback_setup(void)
>                        "qp %u on cryptodev %u",
>                        qp_id, ts_params->valid_devs[0]);
>
> -     TEST_ASSERT(enq_cb_called == true, "Crypto enqueue callback not
> called");
> +     TEST_ASSERT(deq_cb_called == true, "Crypto dequeue callback not
> +called");
>
>        return TEST_SUCCESS;
>  }
> --
> 2.25.1

[-- Attachment #2: Type: text/html, Size: 5068 bytes --]

      reply	other threads:[~2025-04-22  8:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07 14:09 Brian Dooley
2025-04-22  6:14 ` Jiang, YuX
2025-04-22  8:05   ` Xueming Li [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=CH3PR12MB8658C018CD477C641D083964A1BB2@CH3PR12MB8658.namprd12.prod.outlook.com \
    --to=xuemingl@nvidia.com \
    --cc=brian.dooley@intel.com \
    --cc=fanzhang.oss@gmail.com \
    --cc=gakhil@marvell.com \
    --cc=stable@dpdk.org \
    --cc=yux.jiang@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).