DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH 0/4] Remove unnecessary null free checks
Date: Wed, 22 Mar 2023 18:04:24 -0700	[thread overview]
Message-ID: <20230323010428.64020-1-stephen@networkplumber.org> (raw)

These were produced by using coccinelle script.
  $ ./devtools/cocci.sh ./devtools/cocci/nullfree.cocci

Stephen Hemminger (4):
  mldev: remove unnecessary null free checks
  ml/cnkx: remove unnecessary null checks
  graph: remove unnicessary null checks
  examples/fips_validation: remove unneeded null checks

 app/test-mldev/test_device_ops.c       |  6 ++----
 app/test-mldev/test_inference_common.c | 24 ++++++++----------------
 app/test-mldev/test_model_ops.c        |  6 ++----
 drivers/ml/cnxk/cn10k_ml_dev.c         |  9 +++------
 drivers/ml/cnxk/cn10k_ml_ops.c         | 12 ++++--------
 examples/fips_validation/main.c        |  6 ++----
 lib/graph/graph_pcap.c                 |  3 +--
 lib/mldev/rte_mldev.c                  |  3 +--
 8 files changed, 23 insertions(+), 46 deletions(-)

-- 
2.39.2


             reply	other threads:[~2023-03-23  1:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23  1:04 Stephen Hemminger [this message]
2023-03-23  1:04 ` [PATCH 1/4] mldev: remove " Stephen Hemminger
2023-03-23  4:06   ` [EXT] " Srikanth Yalavarthi
2023-03-23  1:04 ` [PATCH 2/4] ml/cnkx: remove unnecessary null checks Stephen Hemminger
2023-03-23  4:14   ` [EXT] " Srikanth Yalavarthi
2023-03-23  1:04 ` [PATCH 3/4] graph: remove unnicessary " Stephen Hemminger
2023-03-23  1:04 ` [PATCH 4/4] examples/fips_validation: remove unneeded " Stephen Hemminger
2023-03-23  9:33 ` [PATCH 0/4] Remove unnecessary null free checks Thomas Monjalon

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=20230323010428.64020-1-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.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).