From: Stephen Hemminger <stephen@networkplumber.org>
To: Wenbo Cao <caowenbo@mucse.com>
Cc: dev@dpdk.org, yaojun@mucse.com
Subject: Re: [PATCH v0 0/3] [v0]drivers/net fixed Coverity issue
Date: Sun, 29 Jun 2025 10:44:20 -0700 [thread overview]
Message-ID: <20250629104420.39505cf0@hermes.local> (raw)
In-Reply-To: <20250618121113.17302-1-caowenbo@mucse.com>
On Wed, 18 Jun 2025 20:11:10 +0800
Wenbo Cao <caowenbo@mucse.com> wrote:
> v1:
> *:fixed compile issue
> v0:
> *:fixed the below issue:
> Coverity issue: 468860,468866,468858
> Fixes: 4530e70f1e32 ("net/rnp: support Tx TSO offload")
> Fixes: 52dfb84e14be ("net/rnp: add device init and uninit")
> Fixes: 52aae4ed4ffb ("net/rnp: add device capabilities")
> *:fixed 64k tso
>
> Wenbo Cao (3):
> net/rnp: add check firmware respond info
> net/rnp: fix Tunnel-TSO VLAN header untrusted loop bound
> net/rnp: fix TSO segmentation for packets of 64KB
>
> drivers/net/rnp/base/rnp_fw_cmd.h | 1 +
> drivers/net/rnp/base/rnp_mbx_fw.c | 15 +++-
> drivers/net/rnp/rnp_ethdev.c | 16 ++--
> drivers/net/rnp/rnp_rxtx.c | 118 +++++++++++++++++++++++-------
> drivers/net/rnp/rnp_rxtx.h | 1 +
> 5 files changed, 117 insertions(+), 34 deletions(-)
>
Overall this patchset looks fine.
Could you try out the suggest bit changes, and resubmit please.
next prev parent reply other threads:[~2025-06-29 17:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 12:11 [PATCH v0 0/3] [v0]drivers/net fixed Coverity issue Wenbo Cao
2025-06-18 12:11 ` [PATCH v1 1/3] net/rnp: add check firmware respond info Wenbo Cao
2025-06-28 22:44 ` Stephen Hemminger
2025-06-18 12:11 ` [PATCH v1 2/3] net/rnp: fix Tunnel-TSO VLAN header untrusted loop bound Wenbo Cao
2025-06-18 12:11 ` [PATCH v1 3/3] net/rnp: fix TSO segmentation for packets of 64KB Wenbo Cao
2025-06-29 17:44 ` Stephen Hemminger [this message]
2025-06-30 6:14 ` [PATCH v0 0/3] [v0]drivers/net fixed Coverity issue 11
-- strict thread matches above, loose matches on Subject: below --
2025-06-18 11:05 Wenbo Cao
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=20250629104420.39505cf0@hermes.local \
--to=stephen@networkplumber.org \
--cc=caowenbo@mucse.com \
--cc=dev@dpdk.org \
--cc=yaojun@mucse.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.