From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Srikanth Yalavarthi <syalavarthi@marvell.com>,
Kai Ji <kai.ji@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
Chengwen Feng <fengchengwen@huawei.com>,
Jeroen de Borst <jeroendb@google.com>,
Rushil Gupta <rushilg@google.com>,
Joshua Washington <joshwash@google.com>,
Devendra Singh Rawat <dsinghrawat@marvell.com>,
Alok Prasad <palok@marvell.com>,
Jochen Behrens <jbehrens@vmware.com>,
Reshma Pattan <reshma.pattan@intel.com>,
Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: Re: [PATCH] memzone: remove unnecessary null checks
Date: Sun, 07 Jul 2024 14:52:43 +0200 [thread overview]
Message-ID: <1858343.e9paKfgaYA@thomas> (raw)
In-Reply-To: <20240619001505.GC13189@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
19/06/2024 02:15, Tyler Retzlaff:
> On Tue, Jun 18, 2024 at 04:25:08PM -0700, Stephen Hemminger wrote:
> > The function rte_memzone_free() already checks if the argument
> > is NULL. Add it to the coccinelle fix script and correct
> > all the existing code.
> >
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> > ---
> Reviewed-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
Acked-by: Morten Brørup <mb@smartsharesystems.com>
Applied, thanks.
next prev parent reply other threads:[~2024-07-07 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 23:25 [PATCH] memzone: remove unnecessary null checks Stephen Hemminger
2024-06-19 0:15 ` Tyler Retzlaff
2024-07-07 12:52 ` Thomas Monjalon [this message]
2024-06-19 7:14 ` Morten Brørup
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=1858343.e9paKfgaYA@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=dsinghrawat@marvell.com \
--cc=fengchengwen@huawei.com \
--cc=jbehrens@vmware.com \
--cc=jeroendb@google.com \
--cc=joshwash@google.com \
--cc=kai.ji@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=palok@marvell.com \
--cc=reshma.pattan@intel.com \
--cc=roretzla@linux.microsoft.com \
--cc=rushilg@google.com \
--cc=stephen@networkplumber.org \
--cc=syalavarthi@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.