From: Akhil Goyal <gakhil@marvell.com>
To: Akhil Goyal <gakhil@marvell.com>, "Ji, Kai" <kai.ji@intel.com>,
Yong Liang <1269690261@qq.com>, "dev@dpdk.org" <dev@dpdk.org>,
Kirill Rybalchenko <kirill.rybalchenko@intel.com>
Subject: RE: [PATCH] crypto/scheduler: fix incorrect variable usage
Date: Wed, 6 Nov 2024 11:53:25 +0000 [thread overview]
Message-ID: <CO6PR18MB44843E5835CD8D0E95F969C3D8532@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CO6PR18MB448492A3B7AFAD4A65645E0ED87F2@CO6PR18MB4484.namprd18.prod.outlook.com>
Hi Kai,
Any update on this patch?
> > I'm not see any issue with original code, can you give more details about crash
> so
> > I can try to reproduce at my end.
> > cc kirill.rybalchenko@intel.com for review
>
> The details are there in Bugzilla
> https://bugs.dpdk.org/show_bug.cgi?id=1537
prev parent reply other threads:[~2024-11-06 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 14:15 Yong Liang
2024-10-07 10:35 ` Ji, Kai
2024-10-09 8:59 ` Akhil Goyal
2024-11-06 11:53 ` Akhil Goyal [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=CO6PR18MB44843E5835CD8D0E95F969C3D8532@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=1269690261@qq.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=kirill.rybalchenko@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).