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, kiran.patil@intel.com,
	netdev@vger.kernel.org, sridhar.samudrala@intel.com,
	amritha.nambiar@intel.com, sudheer.mogilappagari@intel.com,
	bharathi.sreenivas@intel.com
Subject: Re: [PATCH net-next 1/1] ice: Add flow director support for channel mode
Date: Thu, 30 Dec 2021 13:30:12 +0000	[thread overview]
Message-ID: <164087101288.9335.11572997117674639575.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211229185433.685930-1-anthony.l.nguyen@intel.com>

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Wed, 29 Dec 2021 10:54:33 -0800 you wrote:
> From: Kiran Patil <kiran.patil@intel.com>
> 
> Add support to enable flow-director filter when multiple TCs are
> configured. Flow director filter can be configured using ethtool
> (--config-ntuple option). When multiple TCs are configured, each
> TC is mapped to an unique HW VSI. So VSI corresponding to queue
> used in filter is identified and flow director context is updated
> with correct VSI while configuring ntuple filter in HW.
> 
> [...]

Here is the summary with links:
  - [net-next,1/1] ice: Add flow director support for channel mode
    https://git.kernel.org/netdev/net-next/c/40319796b732

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



      reply	other threads:[~2021-12-30 13:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29 18:54 [PATCH net-next 1/1] ice: Add flow director support for channel mode Tony Nguyen
2021-12-30 13:30 ` 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=164087101288.9335.11572997117674639575.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=amritha.nambiar@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=bharathi.sreenivas@intel.com \
    --cc=davem@davemloft.net \
    --cc=kiran.patil@intel.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sridhar.samudrala@intel.com \
    --cc=sudheer.mogilappagari@intel.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.