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, pabeni@redhat.com,
	edumazet@google.com, netdev@vger.kernel.org, sassmann@redhat.com
Subject: Re: [PATCH net 0/2][pull request] Intel Wired LAN Driver Updates 2022-06-30
Date: Fri, 01 Jul 2022 10:40:15 +0000	[thread overview]
Message-ID: <165667201514.26485.7770729375287574254.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220630214940.3036250-1-anthony.l.nguyen@intel.com>

Hello:

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

On Thu, 30 Jun 2022 14:49:38 -0700 you wrote:
> This series contains updates to i40e driver only.
> 
> Lukasz adds reporting of packets dropped for being too large into the Rx
> dropped statistics.
> 
> Norbert clears VF filter and MAC address to resolve issue with older VFs
> being unable to change their MAC address.
> 
> [...]

Here is the summary with links:
  - [net,1/2] i40e: Fix dropped jumbo frames statistics
    https://git.kernel.org/netdev/net/c/1adb1563e7b7
  - [net,2/2] i40e: Fix VF's MAC Address change on VM
    https://git.kernel.org/netdev/net/c/fed0d9f13266

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-07-01 10:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30 21:49 [PATCH net 0/2][pull request] Intel Wired LAN Driver Updates 2022-06-30 Tony Nguyen
2022-06-30 21:49 ` [PATCH net 1/2] i40e: Fix dropped jumbo frames statistics Tony Nguyen
2022-07-01  4:02   ` Jakub Kicinski
2022-06-30 21:49 ` [PATCH net 2/2] i40e: Fix VF's MAC Address change on VM Tony Nguyen
2022-07-01 10:40 ` 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=165667201514.26485.7770729375287574254.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --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.