netdev.vger.kernel.org archive mirror
 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
Subject: Re: [PATCH net-next 0/2][pull request] 40GbE Intel Wired LAN Driver Updates 2022-07-22
Date: Mon, 25 Jul 2022 13:20:13 +0000	[thread overview]
Message-ID: <165875521357.10499.3341972627265684776.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220722175313.112518-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 Fri, 22 Jul 2022 10:53:11 -0700 you wrote:
> This series contains updates to i40e and iavf drivers.
> 
> Przemyslaw adds a helper function for determining whether TC MQPRIO is
> enabled for i40e.
> 
> Avinash utilizes the driver's bookkeeping of filters to check for
> duplicate filter before sending the request to the PF for iavf.
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] i40e: Refactor tc mqprio checks
    https://git.kernel.org/netdev/net-next/c/2313e69c84c0
  - [net-next,2/2] iavf: Check for duplicate TC flower filter before parsing
    https://git.kernel.org/netdev/net-next/c/40e589ba133c

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-25 13:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22 17:53 [PATCH net-next 0/2][pull request] 40GbE Intel Wired LAN Driver Updates 2022-07-22 Tony Nguyen
2022-07-22 17:53 ` [PATCH net-next 1/2] i40e: Refactor tc mqprio checks Tony Nguyen
2022-07-22 17:53 ` [PATCH net-next 2/2] iavf: Check for duplicate TC flower filter before parsing Tony Nguyen
2022-07-25 13: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=165875521357.10499.3341972627265684776.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 \
    /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).