From: patchwork-bot+netdevbpf@kernel.org
To: Simon Horman <simon.horman@corigine.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
michael.chan@broadcom.com, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, shshaikh@marvell.com,
manishc@marvell.com, bin.chen@corigine.com,
GR-Linux-NIC-Dev@marvell.com, netdev@vger.kernel.org,
oss-drivers@corigine.com
Subject: Re: [PATCH net-next] ethernet: Remove vf rate limit check for drivers
Date: Sat, 11 Jun 2022 05:30:12 +0000 [thread overview]
Message-ID: <165492541280.21310.3317091740668140358.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220609084717.155154-1-simon.horman@corigine.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 9 Jun 2022 10:47:17 +0200 you wrote:
> From: Bin Chen <bin.chen@corigine.com>
>
> The commit a14857c27a50 ("rtnetlink: verify rate parameters for calls to
> ndo_set_vf_rate") has been merged to master, so we can to remove the
> now-duplicate checks in drivers.
>
> Signed-off-by: Bin Chen <bin.chen@corigine.com>
> Signed-off-by: Baowen Zheng <baowen.zheng@corigine.com>
> Signed-off-by: Simon Horman <simon.horman@corigine.com>
>
> [...]
Here is the summary with links:
- [net-next] ethernet: Remove vf rate limit check for drivers
https://git.kernel.org/netdev/net-next/c/10e11aa241b6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-06-11 5:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 8:47 [PATCH net-next] ethernet: Remove vf rate limit check for drivers Simon Horman
2022-06-11 5:22 ` Jakub Kicinski
2022-06-12 7:50 ` Simon Horman
2022-06-11 5: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=165492541280.21310.3317091740668140358.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=anthony.l.nguyen@intel.com \
--cc=bin.chen@corigine.com \
--cc=davem@davemloft.net \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=manishc@marvell.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=shshaikh@marvell.com \
--cc=simon.horman@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 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.