All of lore.kernel.org
 help / color / mirror / Atom feed
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: [PATCH net-next 0/7][pull request] 40GbE Intel Wired LAN Driver Updates 2021-02-10
Date: Thu, 11 Feb 2021 21:10:09 +0000	[thread overview]
Message-ID: <161307780999.4804.16367743746327065658.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210210232436.4084373-1-anthony.l.nguyen@intel.com>

Hello:

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

On Wed, 10 Feb 2021 15:24:29 -0800 you wrote:
> This series contains updates to i40e driver only.
> 
> Arkadiusz adds support for software controlled DCB. Upon disabling of the
> firmware LLDP agent, the driver configures DCB with default values
> (only one Traffic Class). At the same time, it allows a software based
> LLDP agent - userspace application i.e. lldpad) to receive DCB TLVs
> and set desired DCB configuration through DCB related netlink callbacks.
> 
> [...]

Here is the summary with links:
  - [net-next,1/7] i40e: Add hardware configuration for software based DCB
    https://git.kernel.org/netdev/net-next/c/90bc8e003be2
  - [net-next,2/7] i40e: Add init and default config of software based DCB
    https://git.kernel.org/netdev/net-next/c/4b208eaa8078
  - [net-next,3/7] i40e: Add netlink callbacks support for software based DCB
    https://git.kernel.org/netdev/net-next/c/5effa78e7c94
  - [net-next,4/7] i40e: Add EEE status getting & setting implementation
    https://git.kernel.org/netdev/net-next/c/95f352dca19d
  - [net-next,5/7] i40e: Add flow director support for IPv6
    https://git.kernel.org/netdev/net-next/c/efca91e89b67
  - [net-next,6/7] i40e: VLAN field for flow director
    https://git.kernel.org/netdev/net-next/c/a9219b332f52
  - [net-next,7/7] i40e: remove the useless value assignment in i40e_clean_adminq_subtask
    https://git.kernel.org/netdev/net-next/c/bfe2e5c44d72

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-02-11 21:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10 23:24 [PATCH net-next 0/7][pull request] 40GbE Intel Wired LAN Driver Updates 2021-02-10 Tony Nguyen
2021-02-10 23:24 ` [PATCH net-next 1/7] i40e: Add hardware configuration for software based DCB Tony Nguyen
2021-02-10 23:24 ` [PATCH net-next 2/7] i40e: Add init and default config of " Tony Nguyen
2021-02-10 23:24 ` [PATCH net-next 3/7] i40e: Add netlink callbacks support for " Tony Nguyen
2021-02-10 23:24 ` [PATCH net-next 4/7] i40e: Add EEE status getting & setting implementation Tony Nguyen
2021-02-10 23:24 ` [PATCH net-next 5/7] i40e: Add flow director support for IPv6 Tony Nguyen
2021-02-10 23:24 ` [PATCH net-next 6/7] i40e: VLAN field for flow director Tony Nguyen
2021-02-10 23:24 ` [PATCH net-next 7/7] i40e: remove the useless value assignment in i40e_clean_adminq_subtask Tony Nguyen
2021-02-11 21:10 ` 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=161307780999.4804.16367743746327065658.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 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.