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 net-next 0/6] net: hns3: updates for -next
Date: Thu, 24 Sep 2020 20:19:42 -0700 (PDT) [thread overview]
Message-ID: <20200924.201942.1679145349636019640.davem@davemloft.net> (raw)
In-Reply-To: <1600993578-41008-1-git-send-email-tanhuazhong@huawei.com>
From: Huazhong Tan <tanhuazhong@huawei.com>
Date: Fri, 25 Sep 2020 08:26:12 +0800
> There are some updates for the HNS3 ethernet driver.
> #1 & #2 are two cleanups.
> #3 adds new hardware error for the client.
> #4 adds debugfs support the pf's interrupt resource.
> #5 adds new pci device id for 200G device.
> #6 renames the unsuitable macro of vf's pci device id.
Series applied, thank you.
next prev parent reply other threads:[~2020-09-25 3:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 0:26 [PATCH net-next 0/6] net: hns3: updates for -next Huazhong Tan
2020-09-25 0:26 ` [PATCH net-next 1/6] net: hns3: refactor the function for dumping tc information in debugfs Huazhong Tan
2020-09-25 0:26 ` [PATCH net-next 2/6] net: hns3: remove unnecessary variable initialization Huazhong Tan
2020-09-25 0:26 ` [PATCH net-next 3/6] net: hns3: add a hardware error detect type Huazhong Tan
2020-09-25 0:26 ` [PATCH net-next 4/6] net: hns3: add debugfs of dumping pf interrupt resources Huazhong Tan
2020-09-25 0:26 ` [PATCH net-next 5/6] net: hns3: add support for 200G device Huazhong Tan
2020-09-25 0:26 ` [PATCH net-next 6/6] net: hns3: rename macro of pci device id of vf Huazhong Tan
2020-09-25 3:19 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-14 12:06 [PATCH net-next 0/6] net: hns3: updates for -next Huazhong Tan
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=20200924.201942.1679145349636019640.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;
as well as URLs for NNTP newsgroup(s).