All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Guangbin Huang <huangguangbin2@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, jiri@nvidia.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	lipeng321@huawei.com, moyufeng@huawei.com,
	chenhao288@hisilicon.com
Subject: Re: [PATCH V3 net-next 0/7] net: hns3: add support devlink
Date: Mon, 26 Jul 2021 11:30:06 +0000	[thread overview]
Message-ID: <162729900676.28679.13330728353268825912.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1627267627-38467-1-git-send-email-huangguangbin2@huawei.com>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Mon, 26 Jul 2021 10:47:00 +0800 you wrote:
> This series adds devlink support for the HNS3 ethernet driver.
> 
> change log:
> V2 -> V3:
> 1. remove two patches of setting rx/tx buffer size by devlink param.
> 
> V1 -> V2:
> 1. add more detailed descriptions of parameters in document hns3.rst.
> 
> [...]

Here is the summary with links:
  - [V3,net-next,1/7] devlink: add documentation for hns3 driver
    https://git.kernel.org/netdev/net-next/c/6149ab604c80
  - [V3,net-next,2/7] net: hns3: add support for registering devlink for PF
    https://git.kernel.org/netdev/net-next/c/b741269b2759
  - [V3,net-next,3/7] net: hns3: add support for registering devlink for VF
    https://git.kernel.org/netdev/net-next/c/cd6242991d2e
  - [V3,net-next,4/7] net: hns3: add support for devlink get info for PF
    https://git.kernel.org/netdev/net-next/c/26fbf511693e
  - [V3,net-next,5/7] net: hns3: add support for devlink get info for VF
    https://git.kernel.org/netdev/net-next/c/bd85e55bfb95
  - [V3,net-next,6/7] net: hns3: add devlink reload support for PF
    https://git.kernel.org/netdev/net-next/c/98fa7525d360
  - [V3,net-next,7/7] net: hns3: add devlink reload support for VF
    https://git.kernel.org/netdev/net-next/c/f2b67226c3a8

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-07-26 11:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-26  2:47 [PATCH V3 net-next 0/7] net: hns3: add support devlink Guangbin Huang
2021-07-26  2:47 ` [PATCH V3 net-next 1/7] devlink: add documentation for hns3 driver Guangbin Huang
2021-07-26  2:47 ` [PATCH V3 net-next 2/7] net: hns3: add support for registering devlink for PF Guangbin Huang
2021-07-26  2:47 ` [PATCH V3 net-next 3/7] net: hns3: add support for registering devlink for VF Guangbin Huang
2021-07-26  2:47 ` [PATCH V3 net-next 4/7] net: hns3: add support for devlink get info for PF Guangbin Huang
2021-07-26  2:47 ` [PATCH V3 net-next 5/7] net: hns3: add support for devlink get info for VF Guangbin Huang
2021-07-26  2:47 ` [PATCH V3 net-next 6/7] net: hns3: add devlink reload support for PF Guangbin Huang
2021-07-26  2:47 ` [PATCH V3 net-next 7/7] net: hns3: add devlink reload support for VF Guangbin Huang
2021-07-26 11:30 ` patchwork-bot+netdevbpf [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=162729900676.28679.13330728353268825912.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=chenhao288@hisilicon.com \
    --cc=davem@davemloft.net \
    --cc=huangguangbin2@huawei.com \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lipeng321@huawei.com \
    --cc=moyufeng@huawei.com \
    --cc=netdev@vger.kernel.org \
    /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.