From: Kevin Traynor <ktraynor@redhat.com>
To: Nipun Gupta <nipun.gupta@nxp.com>
Cc: stable@dpdk.org, Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: Re: [dpdk-stable] [PATCH 18.11] test/crypto: fix session init failure for wireless case
Date: Wed, 18 Dec 2019 11:22:44 +0000 [thread overview]
Message-ID: <e2ae0ec7-70d9-90ce-4862-3e6860b69ced@redhat.com> (raw)
In-Reply-To: <20191218044527.12485-1-nipun.gupta@nxp.com>
On 18/12/2019 04:45, Nipun Gupta wrote:
> From: Hemant Agrawal <hemant.agrawal@nxp.com>
>
> This patch add the support to handle the failure in session
> create for wireless related cases. Else it will cause
> segment fault due to I/O on un-initialized sessions.
>
> Fixes: b3bbd9e5f2659 ("cryptodev: support device independent sessions")
> Cc: stable@dpdk.org
>
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
Thanks Nipun, added upstream commit/removed stable tag and applied.
prev parent reply other threads:[~2019-12-18 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 4:45 Nipun Gupta
2019-12-18 11:22 ` Kevin Traynor [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=e2ae0ec7-70d9-90ce-4862-3e6860b69ced@redhat.com \
--to=ktraynor@redhat.com \
--cc=hemant.agrawal@nxp.com \
--cc=nipun.gupta@nxp.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).