From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
sassmann@redhat.com
Subject: Re: [net-next v2 0/3][pull request] 40GbE Intel Wired LAN Driver Updates 2020-11-24
Date: Thu, 26 Nov 2020 02:20:06 +0000 [thread overview]
Message-ID: <160635720619.6662.10189294280132606321.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201124165245.2844118-1-anthony.l.nguyen@intel.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Tue, 24 Nov 2020 08:52:42 -0800 you wrote:
> This series contains updates to i40e and igbvf drivers.
>
> Marek removes a redundant assignment for i40e.
>
> Stefan Assmann corrects reporting of VF link speed for i40e.
>
> Karen revises a couple of error messages to warnings for igbvf as they
> could be misinterpreted as issues when they are not.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/3] i40e: remove redundant assignment
https://git.kernel.org/netdev/net-next/c/088d5360d05a
- [net-next,v2,2/3] i40e: report correct VF link speed when link state is set to enable
https://git.kernel.org/netdev/net-next/c/6ec12e1e9404
- [net-next,v2,3/3] igbvf: Refactor traces
https://git.kernel.org/netdev/net-next/c/24453a84285e
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:[~2020-11-26 2:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 16:52 [net-next v2 0/3][pull request] 40GbE Intel Wired LAN Driver Updates 2020-11-24 Tony Nguyen
2020-11-24 16:52 ` [net-next v2 1/3] i40e: remove redundant assignment Tony Nguyen
2020-11-24 16:52 ` [net-next v2 2/3] i40e: report correct VF link speed when link state is set to enable Tony Nguyen
2020-11-24 16:52 ` [net-next v2 3/3] igbvf: Refactor traces Tony Nguyen
2020-11-26 2:20 ` 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=160635720619.6662.10189294280132606321.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sassmann@redhat.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).