From: Akhil Goyal <gakhil@marvell.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXT] [PATCH 0/2] remove unnecessary null checks in OpenSSL usage
Date: Thu, 9 Nov 2023 20:12:24 +0000 [thread overview]
Message-ID: <CO6PR18MB4484C1473C7C0D667CF08FDBD8AFA@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20231102230307.6138-1-stephen@networkplumber.org>
> OpenSSL follows null free conventions
>
> Stephen Hemminger (2):
> nullfree: add matches for null free cases from OpenSSL
> crypto/openssl: remove unnecessary NULL checks before free
>
> devtools/cocci/nullfree.cocci | 9 +++++
> drivers/crypto/openssl/rte_openssl_pmd.c | 36 +++++++-------------
> drivers/crypto/openssl/rte_openssl_pmd_ops.c | 3 +-
> 3 files changed, 22 insertions(+), 26 deletions(-)
Series Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2023-11-09 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 23:02 Stephen Hemminger
2023-11-02 23:02 ` [PATCH 1/2] nullfree: add matches for null free cases from OpenSSL Stephen Hemminger
2023-11-02 23:02 ` [PATCH 2/2] crypto/openssl: remove unnecessary NULL checks before free Stephen Hemminger
2023-11-07 14:12 ` Ji, Kai
2023-11-09 20:12 ` 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=CO6PR18MB4484C1473C7C0D667CF08FDBD8AFA@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).