From: Akhil Goyal <gakhil@marvell.com>
To: Volodymyr Fialko <vfialko@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Radu Nicolau <radu.nicolau@intel.com>,
Volodymyr Fialko <vfialko@marvell.com>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Anoob Joseph <anoobj@marvell.com>
Subject: RE: [PATCH] examples/ipsec-secgw: fix uninitialized variable access
Date: Thu, 10 Nov 2022 14:14:16 +0000 [thread overview]
Message-ID: <CO6PR18MB4484FE2908FA718DB6F138BDD8019@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20221109095237.1773458-1-vfialko@marvell.com>
> Subject: [PATCH] examples/ipsec-secgw: fix uninitialized variable access
>
> Fix uninitialized variable access of outbound offloads flags.
>
> Coverity issue: 381669
> Fixes: 6938fc92c404 ("examples/ipsec-secgw: add lookaside event mode")
>
> Signed-off-by: Volodymyr Fialko <vfialko@marvell.com>
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2022-11-10 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 9:52 Volodymyr Fialko
2022-11-10 14:14 ` 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=CO6PR18MB4484FE2908FA718DB6F138BDD8019@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=radu.nicolau@intel.com \
--cc=vfialko@marvell.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).