From: Akhil Goyal <gakhil@marvell.com>
To: Thierry Herbelot <thierry.herbelot@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>,
"stable@dpdk.org" <stable@dpdk.org>,
Declan Doherty <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [EXT] [PATCH] test/test_cryptodev: do not use a possibly NULL Pointer
Date: Tue, 29 Jun 2021 20:34:46 +0000 [thread overview]
Message-ID: <CO6PR18MB4484A71BD4DDE04F8081680DD8029@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20210524090113.16748-1-thierry.herbelot@6wind.com>
> Use m only after it was checked not to be NULL.
>
> Fixes: 202d375c60bc1 ("app/test: add cryptodev unit and performance
> tests")
> Cc: stable@dpdk.org
> Cc: Declan Doherty <declan.doherty@intel.com>
>
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2021-06-29 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 9:01 [dpdk-dev] " Thierry Herbelot
2021-06-29 20:34 ` 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=CO6PR18MB4484A71BD4DDE04F8081680DD8029@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=thierry.herbelot@6wind.com \
--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).