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 2022-03-01
Date: Thu, 03 Mar 2022 06:20:12 +0000	[thread overview]
Message-ID: <164628841283.5215.15039723753643376506.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220301185939.3005116-1-anthony.l.nguyen@intel.com>

Hello:

This series was applied to netdev/net-next.git (master)
by Tony Nguyen <anthony.l.nguyen@intel.com>:

On Tue,  1 Mar 2022 10:59:32 -0800 you wrote:
> This series contains updates to iavf driver only.
> 
> Mateusz adds support for interrupt moderation for 50G and 100G speeds
> as well as support for the driver to specify a request as its primary
> MAC address. He also refactors VLAN V2 capability exchange into more
> generic extended capabilities to ease the addition of future
> capabilities. Finally, he corrects the incorrect return of iavf_status
> values and removes non-inclusive language.
> 
> [...]

Here is the summary with links:
  - [net-next,1/7] iavf: Add support for 50G/100G in AIM algorithm
    https://git.kernel.org/netdev/net-next/c/d73dd1275e70
  - [net-next,2/7] iavf: refactor processing of VLAN V2 capability message
    https://git.kernel.org/netdev/net-next/c/87dba256c7a6
  - [net-next,3/7] iavf: Add usage of new virtchnl format to set default MAC
    https://git.kernel.org/netdev/net-next/c/a3e839d539e0
  - [net-next,4/7] iavf: remove redundant ret variable
    https://git.kernel.org/netdev/net-next/c/c3fec56e1267
  - [net-next,5/7] iavf: stop leaking iavf_status as "errno" values
    https://git.kernel.org/netdev/net-next/c/bae569d01a1f
  - [net-next,6/7] iavf: Fix incorrect use of assigning iavf_status to int
    https://git.kernel.org/netdev/net-next/c/8fc16be67dba
  - [net-next,7/7] iavf: Remove non-inclusive language
    https://git.kernel.org/netdev/net-next/c/0a62b2098987

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



      parent reply	other threads:[~2022-03-03  6:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 18:59 [PATCH net-next 0/7][pull request] 40GbE Intel Wired LAN Driver Updates 2022-03-01 Tony Nguyen
2022-03-01 18:59 ` [PATCH net-next 1/7] iavf: Add support for 50G/100G in AIM algorithm Tony Nguyen
2022-03-01 18:59 ` [PATCH net-next 2/7] iavf: refactor processing of VLAN V2 capability message Tony Nguyen
2022-03-01 18:59 ` [PATCH net-next 3/7] iavf: Add usage of new virtchnl format to set default MAC Tony Nguyen
2022-03-01 18:59 ` [PATCH net-next 4/7] iavf: remove redundant ret variable Tony Nguyen
2022-03-01 18:59 ` [PATCH net-next 5/7] iavf: stop leaking iavf_status as "errno" values Tony Nguyen
2022-03-01 18:59 ` [PATCH net-next 6/7] iavf: Fix incorrect use of assigning iavf_status to int Tony Nguyen
2022-03-01 18:59 ` [PATCH net-next 7/7] iavf: Remove non-inclusive language Tony Nguyen
2022-03-03  6: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=164628841283.5215.15039723753643376506.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.