From: "Jiang, YuX" <yux.jiang@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>,
Luca Boccassi <luca.boccassi@gmail.com>
Cc: "Ji, Kai" <kai.ji@intel.com>,
"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"Jiang, YuX" <yux.jiang@intel.com>
Subject: RE: [PATCH 22.11] app/test: fix a merge problem in oop patch
Date: Tue, 1 Apr 2025 08:39:02 +0000 [thread overview]
Message-ID: <CYYPR11MB8331EF01271FA09222A97191FEAC2@CYYPR11MB8331.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20250331213220.3268748-1-arkadiuszx.kusztal@intel.com>
> -----Original Message-----
> From: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
> Sent: Tuesday, April 1, 2025 5:32 AM
> To: stable@dpdk.org
> Cc: Ji, Kai <kai.ji@intel.com>; Kusztal, ArkadiuszX
> <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH 22.11] app/test: fix a merge problem in oop patch
>
> Fix "app/test: fix the check of the oop header data" was incorrectly
> applied: code was added into the wrong functions. This fix addresses this
> issue.
>
> Bugzilla ID: 1686
> Fixes: bb8feaacb489 ("test/crypto: fix check for OOP header data")
>
> Signed-off-by: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
> ---
> app/test/test_cryptodev.c | 58 +++++++++++++++++++--------------------
> 1 file changed, 29 insertions(+), 29 deletions(-)
>
This patch can fix bug: Bugzilla ID: 1686.
Thanks all.
Tested-by: Jiang, YuX <yux.jiang@intel.com>
Best regards,
Yu Jiang
next prev parent reply other threads:[~2025-04-01 8:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 21:32 Arkadiusz Kusztal
2025-04-01 8:39 ` Jiang, YuX [this message]
2025-04-01 13:54 ` Luca Boccassi
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=CYYPR11MB8331EF01271FA09222A97191FEAC2@CYYPR11MB8331.namprd11.prod.outlook.com \
--to=yux.jiang@intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=kai.ji@intel.com \
--cc=luca.boccassi@gmail.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).