From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Junlong Wang <wang.junlong1@zte.com.cn>,
Lijie Shan <shan.lijie@zte.com.cn>
Subject: Re: [PATCH 3/4] net/zxdh: remove unnecessary null check
Date: Sun, 12 Apr 2026 09:22:48 -0700 [thread overview]
Message-ID: <20260412092248.295f72f4@phoenix.local> (raw)
In-Reply-To: <20260401164108.201404-4-stephen@networkplumber.org>
On Wed, 1 Apr 2026 09:40:24 -0700
Stephen Hemminger <stephen@networkplumber.org> wrote:
> No need to check for null before calling free.
> Found by coccinelle script null_free.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
Trivial, applied to next-net
next prev parent reply other threads:[~2026-04-12 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 16:40 [PATCH 0/4] remove useless null checks before free Stephen Hemminger
2026-04-01 16:40 ` [PATCH 1/4] net/ice: remove unnecessary null check Stephen Hemminger
2026-04-01 16:44 ` Bruce Richardson
2026-04-01 16:40 ` [PATCH 2/4] net/bnxt: " Stephen Hemminger
2026-04-01 16:40 ` [PATCH 3/4] net/zxdh: " Stephen Hemminger
2026-04-12 16:22 ` Stephen Hemminger [this message]
2026-04-01 16:40 ` [PATCH 4/4] app/test_compress: " Stephen Hemminger
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=20260412092248.295f72f4@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=shan.lijie@zte.com.cn \
--cc=wang.junlong1@zte.com.cn \
/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