DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 0/3] unnecessary checks for null
Date: Tue, 12 Nov 2024 20:56:49 -0800	[thread overview]
Message-ID: <20241112205649.56123625@hermes.local> (raw)
In-Reply-To: <03775b2e-3187-4027-b646-c33ece294ef4@amd.com>

On Wed, 13 Nov 2024 01:25:37 +0000
Ferruh Yigit <ferruh.yigit@amd.com> wrote:

> On 11/12/2024 5:38 PM, Stephen Hemminger wrote:
> > Found by running nullfree.cocci on 24.11-rc2
> > 
> > Stephen Hemminger (3):
> >   bus/fslmc: remove unnecessary null check
> >   net/dpaa2: remove unnecessary check for null before rte_free
> >   net/ntnic: remove unnecessary check for null before free
> >  
> 
> For series,
> Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
> 
> Btw, script catches 'rte_openssl_pmd.c' for 'EVP_PKEY_free()' call,
> which seems ignoring the NULL value, it can be separate patch for crypto
> tree.

Right I wanted to check that one more carefully.

      reply	other threads:[~2024-11-13  4:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12 17:38 Stephen Hemminger
2024-11-12 17:38 ` [PATCH 1/3] bus/fslmc: remove unnecessary null check Stephen Hemminger
2024-11-13  5:01   ` Hemant Agrawal
2024-11-12 17:38 ` [PATCH 2/3] net/dpaa2: remove unnecessary check for null before rte_free Stephen Hemminger
2024-11-13  5:01   ` Hemant Agrawal
2024-11-12 17:38 ` [PATCH 3/3] net/ntnic: remove unnecessary check for null before free Stephen Hemminger
2024-11-13  1:25 ` [PATCH 0/3] unnecessary checks for null Ferruh Yigit
2024-11-13  4:56   ` Stephen Hemminger [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=20241112205649.56123625@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.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).