From: Akhil Goyal <akhil.goyal@nxp.com>
To: Akhil Goyal <akhil.goyal@nxp.com>, Thomas Monjalon <thomas@monjalon.net>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
Bernard Iremonger <bernard.iremonger@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-stable] [PATCH] examples/ipsec-secgw: fix unchecked return value
Date: Thu, 19 Sep 2019 14:55:20 +0000 [thread overview]
Message-ID: <DB8PR04MB66353C44CE2A8C84E8C41705E6890@DB8PR04MB6635.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <VE1PR04MB66398FC28FB5513DC4DA9D4BE6D60@VE1PR04MB6639.eurprd04.prod.outlook.com>
>
> >
> > 07/08/2019 15:39, Akhil Goyal:
> > >
> > > >
> > > > Check the return value of the rte_eth_dev_rss_hash_conf_get
> function.
> > > >
> > > > Coverity issue: 344970
> > > > Fixes: 3a690d5a65e2 ("examples/ipsec-secgw: fix first packet with inline
> > crypto")
> > > > Cc: stable@dpdk.org
> > > >
> > > > Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
> > > > ---
> > > Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
> > >
> > > Thomas,
> > > Could you please take this patch directly to master.
> >
> > It doesn't look critical at all.
> > Why do you want this in DPDK 19.08 without enough time for proper
> validation
> > testing?
> Yes this one is not a critical fix. We can defer it to next release.
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2019-09-19 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 12:30 Bernard Iremonger
2019-08-07 13:39 ` Akhil Goyal
2019-08-08 7:22 ` Thomas Monjalon
2019-08-09 10:21 ` Akhil Goyal
2019-09-19 14:55 ` 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=DB8PR04MB66353C44CE2A8C84E8C41705E6890@DB8PR04MB6635.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).