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,
	ahmed.zaki@intel.com
Subject: Re: [PATCH net v2 0/2][pull request] iavf: fix racing in VLANs
Date: Wed, 12 Apr 2023 04:40:18 +0000	[thread overview]
Message-ID: <168127441844.15405.2875889687278679287.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230407210730.3046149-1-anthony.l.nguyen@intel.com>

Hello:

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

On Fri,  7 Apr 2023 14:07:28 -0700 you wrote:
> Ahmed Zaki says:
> 
> This patchset mainly fixes a racing issue in the iavf where the number of
> VLANs in the vlan_filter_list might be more than the PF limit. To fix that,
> we get rid of the cvlans and svlans bitmaps and keep all the required info
> in the list.
> 
> [...]

Here is the summary with links:
  - [net,v2,1/2] iavf: refactor VLAN filter states
    https://git.kernel.org/netdev/net/c/0c0da0e95105
  - [net,v2,2/2] iavf: remove active_cvlans and active_svlans bitmaps
    https://git.kernel.org/netdev/net/c/9c85b7fa12ef

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



      parent reply	other threads:[~2023-04-12  4:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07 21:07 [PATCH net v2 0/2][pull request] iavf: fix racing in VLANs Tony Nguyen
2023-04-07 21:07 ` [PATCH net v2 1/2] iavf: refactor VLAN filter states Tony Nguyen
2023-04-09 10:40   ` Leon Romanovsky
2023-04-07 21:07 ` [PATCH net v2 2/2] iavf: remove active_cvlans and active_svlans bitmaps Tony Nguyen
2023-04-09 10:40   ` Leon Romanovsky
2023-04-12  4: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=168127441844.15405.2875889687278679287.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ahmed.zaki@intel.com \
    --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 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.