From: Chaoyong He <chaoyong.he@corigine.com>
To: dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com,
Chaoyong He <chaoyong.he@corigine.com>
Subject: [PATCH 0/3] fix wrong increment of free list counter
Date: Fri, 18 Nov 2022 09:44:05 +0800 [thread overview]
Message-ID: <20221118014408.19565-1-chaoyong.he@corigine.com> (raw)
The wrong increment of free list counter occurs three different place,
and is imported by different commit.
Chaoyong He (3):
net/nfp: fix wrong increment of free list counter
net/nfp: fix wrong increment of free list counter for PF
net/nfp: fix wrong increment of free list counter for VNIC
drivers/net/nfp/flower/nfp_flower.c | 3 +--
drivers/net/nfp/flower/nfp_flower_ctrl.c | 3 +--
drivers/net/nfp/nfp_rxtx.c | 3 +--
3 files changed, 3 insertions(+), 6 deletions(-)
--
2.29.3
next reply other threads:[~2022-11-18 1:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 1:44 Chaoyong He [this message]
2022-11-18 1:44 ` [PATCH 1/3] net/nfp: " Chaoyong He
2022-11-18 14:04 ` Ferruh Yigit
2022-11-18 1:44 ` [PATCH 2/3] net/nfp: fix wrong increment of free list counter for PF Chaoyong He
2022-11-18 1:44 ` [PATCH 3/3] net/nfp: fix wrong increment of free list counter for VNIC Chaoyong He
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=20221118014408.19565-1-chaoyong.he@corigine.com \
--to=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=niklas.soderlund@corigine.com \
--cc=oss-drivers@corigine.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).