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, jesse.brandeburg@intel.com
Subject: Re: [PATCH net-next 0/3][pull request] 100GbE Intel Wired LAN Driver Updates 2021-06-18
Date: Fri, 18 Jun 2021 20:20:04 +0000 [thread overview]
Message-ID: <162404760466.11552.1483547432976975900.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210618162932.859071-1-anthony.l.nguyen@intel.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Fri, 18 Jun 2021 09:29:29 -0700 you wrote:
> Jesse Brandeburg says:
>
> Update three of the Intel Ethernet drivers with similar (but not the
> same) improvements to simplify the packet type table init, while removing
> an unused structure entry. For the ice driver, the table is extended
> to 10 bits, which is the hardware limit, and for now is initialized
> to zero.
>
> [...]
Here is the summary with links:
- [net-next,1/3] ice: report hash type such as L2/L3/L4
https://git.kernel.org/netdev/net-next/c/dda90cb90a5c
- [net-next,2/3] i40e: clean up packet type lookup table
https://git.kernel.org/netdev/net-next/c/c6e088bf30dc
- [net-next,3/3] iavf: clean up packet type lookup table
https://git.kernel.org/netdev/net-next/c/37dc8fea8656
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:[~2021-06-18 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 16:29 [PATCH net-next 0/3][pull request] 100GbE Intel Wired LAN Driver Updates 2021-06-18 Tony Nguyen
2021-06-18 16:29 ` [PATCH net-next 1/3] ice: report hash type such as L2/L3/L4 Tony Nguyen
2021-06-18 16:29 ` [PATCH net-next 2/3] i40e: clean up packet type lookup table Tony Nguyen
2021-06-18 16:29 ` [PATCH net-next 3/3] iavf: " Tony Nguyen
2021-06-18 20: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=162404760466.11552.1483547432976975900.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=jesse.brandeburg@intel.com \
--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).