From: David Miller <davem@davemloft.net>
To: tanhuazhong@huawei.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
salil.mehta@huawei.com, yisen.zhuang@huawei.com,
linuxarm@huawei.com, kuba@kernel.org
Subject: Re: [PATCH V2 net-next 0/9] net: hns3: refactor for MAC table
Date: Sat, 25 Apr 2020 20:57:08 -0700 (PDT) [thread overview]
Message-ID: <20200425.205708.525782253974441.davem@davemloft.net> (raw)
In-Reply-To: <f1d27955-7ffc-7569-9038-17bff854af02@huawei.com>
From: tanhuazhong <tanhuazhong@huawei.com>
Date: Sun, 26 Apr 2020 11:44:18 +0800
> This V2 only adds patch #9 in V1. Since V1 has applied, could you pick
> patch #9 from V2, or i just resend patch #9?
I applied patch #9 from V2.
prev parent reply other threads:[~2020-04-26 3:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 2:13 Huazhong Tan
2020-04-26 2:13 ` [PATCH V2 net-next 1/9] net: hns3: refine for unicast MAC VLAN space management Huazhong Tan
2020-04-26 2:13 ` [PATCH V2 net-next 2/9] net: hns3: remove unnecessary parameter 'is_alloc' in hclge_set_umv_space() Huazhong Tan
2020-04-26 2:13 ` [PATCH V2 net-next 3/9] net: hns3: replace num_req_vfs with num_alloc_vport in hclge_reset_umv_space() Huazhong Tan
2020-04-26 2:13 ` [PATCH V2 net-next 4/9] net: hns3: refactor the MAC address configure Huazhong Tan
2020-04-26 2:13 ` [PATCH V2 net-next 5/9] net: hns3: add support for dumping UC and MC MAC list Huazhong Tan
2020-04-26 2:13 ` [PATCH V2 net-next 6/9] net: hns3: refactor the promisc mode setting Huazhong Tan
2020-04-26 2:13 ` [PATCH V2 net-next 7/9] net: hns3: use mutex vport_lock instead of mutex umv_lock Huazhong Tan
2020-04-26 2:13 ` [PATCH V2 net-next 8/9] net: hns3: optimize the filter table entries handling when resetting Huazhong Tan
2020-04-26 2:13 ` [PATCH V2 net-next 9/9] net: hns3: remove an unnecessary check in hclge_set_umv_space() Huazhong Tan
2020-04-26 3:44 ` [PATCH V2 net-next 0/9] net: hns3: refactor for MAC table tanhuazhong
2020-04-26 3:57 ` David Miller [this message]
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=20200425.205708.525782253974441.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=tanhuazhong@huawei.com \
--cc=yisen.zhuang@huawei.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
all inboxes | Powered by JetHome®