From: "Min Hu (Connor)" <humin29@huawei.com>
To: <dev@dpdk.org>
Cc: <ferruh.yigit@intel.com>, <thomas@monjalon.net>
Subject: [PATCH 0/2] bugfix for bonding
Date: Fri, 28 Jan 2022 10:25:31 +0800 [thread overview]
Message-ID: <20220128022533.44249-1-humin29@huawei.com> (raw)
Two bugfixed for bonding.
Min Hu (Connor) (2):
net/bonding: fix promiscuous and allmulticast state
net/bonding: fix reference count on mbufs
drivers/net/bonding/rte_eth_bond_pmd.c | 72 +++++++++++++++++++++++++-
1 file changed, 71 insertions(+), 1 deletion(-)
--
2.33.0
next reply other threads:[~2022-01-28 2:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 2:25 Min Hu (Connor) [this message]
2022-01-28 2:25 ` [PATCH 1/2] net/bonding: fix promiscuous and allmulticast state Min Hu (Connor)
2022-01-28 2:25 ` [PATCH 2/2] net/bonding: fix reference count on mbufs Min Hu (Connor)
2022-01-31 14:19 ` [PATCH 0/2] bugfix for bonding Ferruh Yigit
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=20220128022533.44249-1-humin29@huawei.com \
--to=humin29@huawei.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=thomas@monjalon.net \
/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).