From: "Min Hu (Connor)" <humin29@huawei.com>
To: <dev@dpdk.org>
Cc: <ferruh.yigit@intel.com>, <cristian.dumitrescu@intel.com>,
<jerinj@marvell.com>, <jianjay.zhou@huawei.com>,
<jia.guo@intel.com>, <g.singh@nxp.com>,
<andrew.rybchenko@oktetlabs.ru>, <hemant.agrawal@nxp.com>,
<orika@nvidia.com>
Subject: [dpdk-dev] [PATCH 00/10] fixes for clean code
Date: Mon, 19 Apr 2021 21:34:39 +0800 [thread overview]
Message-ID: <1618839289-33224-1-git-send-email-humin29@huawei.com> (raw)
This patchset fix some bugs, to make the code more clean.
Chengchang Tang (1):
net/bonding: fix configuration assignment overflow
HongBo Zheng (5):
app/test: add NULL pointer check of memory allocation
lib/librte_pipeline: fix the use of unsafe strcpy
examples/l3fwd: add function return value check
crypto/virtio: fix return values check error
net/e1000: add function return value check
Min Hu (Connor) (4):
net/pfe: check return value
common/sfc_efx/base: delete redundant handling
bus/dpaa: fix management command init calling
app/regex: fix division by zero
app/test-regex/main.c | 8 +++++---
app/test/test_crc.c | 2 ++
drivers/bus/dpaa/base/qbman/bman.c | 6 ++----
drivers/common/sfc_efx/base/rhead_nic.c | 3 +--
drivers/crypto/virtio/virtio_rxtx.c | 4 ++--
drivers/net/bonding/rte_eth_bond_8023ad.c | 2 +-
drivers/net/e1000/base/e1000_ich8lan.c | 2 ++
drivers/net/pfe/pfe_ethdev.c | 6 ++++++
examples/l3fwd/l3fwd_event.c | 6 +++++-
lib/librte_pipeline/rte_swx_pipeline.c | 4 ++--
10 files changed, 28 insertions(+), 15 deletions(-)
--
2.7.4
next reply other threads:[~2021-04-19 13:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 13:34 Min Hu (Connor) [this message]
2021-04-19 13:34 ` [dpdk-dev] [PATCH 01/10] net/pfe: check return value Min Hu (Connor)
2023-06-30 17:59 ` Stephen Hemminger
2021-04-19 13:34 ` [dpdk-dev] [PATCH 02/10] common/sfc_efx/base: delete redundant handling Min Hu (Connor)
2021-04-20 9:33 ` Andrew Rybchenko
2021-04-20 9:42 ` Min Hu (Connor)
2021-04-19 13:34 ` [dpdk-dev] [PATCH 03/10] bus/dpaa: fix management command init calling Min Hu (Connor)
2021-04-20 9:35 ` Andrew Rybchenko
2021-04-20 9:54 ` Min Hu (Connor)
2021-04-19 13:34 ` [dpdk-dev] [PATCH 04/10] app/regex: fix division by zero Min Hu (Connor)
2021-04-19 17:48 ` Ori Kam
2021-04-19 13:34 ` [dpdk-dev] [PATCH 05/10] app/test: add null pointer check of memory allocation Min Hu (Connor)
2022-06-26 17:48 ` Thomas Monjalon
2021-04-19 13:34 ` [dpdk-dev] [PATCH 06/10] lib/librte_pipeline: fix the use of unsafe strcpy Min Hu (Connor)
2021-04-20 9:36 ` Andrew Rybchenko
2023-06-30 18:08 ` Stephen Hemminger
2023-07-03 10:57 ` Dumitrescu, Cristian
2021-04-19 13:34 ` [dpdk-dev] [PATCH 07/10] examples/l3fwd: add function return value check Min Hu (Connor)
2023-06-30 18:15 ` Stephen Hemminger
2021-04-19 13:34 ` [dpdk-dev] [PATCH 08/10] crypto/virtio: fix return values check error Min Hu (Connor)
2023-06-30 18:14 ` Stephen Hemminger
2021-04-19 13:34 ` [dpdk-dev] [PATCH 09/10] net/e1000: add function return value check Min Hu (Connor)
2021-04-19 13:34 ` [dpdk-dev] [PATCH 10/10] net/bonding: fix configuration assignment overflow Min Hu (Connor)
2023-06-30 18:02 ` 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=1618839289-33224-1-git-send-email-humin29@huawei.com \
--to=humin29@huawei.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=g.singh@nxp.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=jia.guo@intel.com \
--cc=jianjay.zhou@huawei.com \
--cc=orika@nvidia.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).