From: "Renyong Wan" <wanry@yunsilicon.com>
To: <dev@dpdk.org>
Cc: <thomas@monjalon.net>, <stephen@networkplumber.org>,
<qianr@yunsilicon.com>, <nana@yunsilicon.com>,
<zhangxx@yunsilicon.com>, <xudw@yunsilicon.com>,
<jacky@yunsilicon.com>, <weihg@yunsilicon.com>,
<zhenghy@yunsilicon.com>
Subject: [PATCH 0/2] net/xsc: Resolve warnings from PVS
Date: Tue, 25 Feb 2025 10:48:17 +0800 [thread overview]
Message-ID: <20250225024810.2489747-1-wanry@yunsilicon.com> (raw)
This patch series resolves two warnings reported by PVS studio.
---
Renyong Wan (2):
net/xsc: check possible null pointer dereference
net/xsc: suppress assign the same value warning
drivers/net/xsc/xsc_rx.c | 6 +++++-
drivers/net/xsc/xsc_vfio_mbox.c | 2 +-
2 files changed, 6 insertions(+), 2 deletions(-)
--
2.25.1
next reply other threads:[~2025-02-25 2:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 2:48 Renyong Wan [this message]
2025-02-25 2:48 ` [PATCH 1/2] net/xsc: check possible null pointer dereference Renyong Wan
2025-02-25 2:48 ` [PATCH 2/2] net/xsc: suppress assign the same value warning Renyong Wan
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=20250225024810.2489747-1-wanry@yunsilicon.com \
--to=wanry@yunsilicon.com \
--cc=dev@dpdk.org \
--cc=jacky@yunsilicon.com \
--cc=nana@yunsilicon.com \
--cc=qianr@yunsilicon.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--cc=weihg@yunsilicon.com \
--cc=xudw@yunsilicon.com \
--cc=zhangxx@yunsilicon.com \
--cc=zhenghy@yunsilicon.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).