All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeed@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, saeedm@nvidia.com, netdev@vger.kernel.org,
	tariqt@nvidia.com, mbloch@nvidia.com, roid@nvidia.com
Subject: Re: [net-next V2 01/14] net/mlx5e: en_tc, Extend peer flows to a list
Date: Mon, 05 Jun 2023 23:00:24 +0000	[thread overview]
Message-ID: <168600602472.28052.8782299631686773162.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230602191301.47004-2-saeed@kernel.org>

Hello:

This series was applied to netdev/net-next.git (main)
by Saeed Mahameed <saeedm@nvidia.com>:

On Fri,  2 Jun 2023 12:12:48 -0700 you wrote:
> From: Mark Bloch <mbloch@nvidia.com>
> 
> Currently, mlx5e_flow is holding a pointer to a peer_flow, in case one
> was created. e.g. There is an assumption that mlx5e_flow can have only
> one peer.
> In order to support more than one peer, refactor mlx5e_flow to hold a
> list of peer flows.
> 
> [...]

Here is the summary with links:
  - [net-next,V2,01/14] net/mlx5e: en_tc, Extend peer flows to a list
    https://git.kernel.org/netdev/net-next/c/953bb24ddc11
  - [net-next,V2,02/14] net/mlx5e: tc, Refactor peer add/del flow
    https://git.kernel.org/netdev/net-next/c/b1661efa4dbb
  - [net-next,V2,03/14] net/mlx5e: rep, store send to vport rules per peer
    https://git.kernel.org/netdev/net-next/c/ed7a8fe71836
  - [net-next,V2,04/14] net/mlx5e: en_tc, re-factor query route port
    https://git.kernel.org/netdev/net-next/c/0af3613ddc91
  - [net-next,V2,05/14] net/mlx5e: Handle offloads flows per peer
    https://git.kernel.org/netdev/net-next/c/9be6c21fdcf8
  - [net-next,V2,06/14] net/mlx5: E-switch, enlarge peer miss group table
    https://git.kernel.org/netdev/net-next/c/18e31d422675
  - [net-next,V2,07/14] net/mlx5: E-switch, refactor FDB miss rule add/remove
    https://git.kernel.org/netdev/net-next/c/9bee385a6e39
  - [net-next,V2,08/14] net/mlx5: E-switch, Handle multiple master egress rules
    https://git.kernel.org/netdev/net-next/c/5e0202eb49ed
  - [net-next,V2,09/14] net/mlx5: E-switch, generalize shared FDB creation
    https://git.kernel.org/netdev/net-next/c/014e4d48eaa3
  - [net-next,V2,10/14] net/mlx5: DR, handle more than one peer domain
    https://git.kernel.org/netdev/net-next/c/6d5b7321d8af
  - [net-next,V2,11/14] net/mlx5: Devcom, Rename paired to ready
    https://git.kernel.org/netdev/net-next/c/e67f928a5204
  - [net-next,V2,12/14] net/mlx5: E-switch, mark devcom as not ready when all eswitches are unpaired
    https://git.kernel.org/netdev/net-next/c/8611df722030
  - [net-next,V2,13/14] net/mlx5: Devcom, introduce devcom_for_each_peer_entry
    https://git.kernel.org/netdev/net-next/c/90ca127c62e9
  - [net-next,V2,14/14] net/mlx5: Devcom, extend mlx5_devcom_send_event to work with more than two devices
    https://git.kernel.org/netdev/net-next/c/e2a82bf8a428

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



  reply	other threads:[~2023-06-05 23:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02 19:12 [pull request][net-next V2 00/14] mlx5 updates 2023-05-31 Saeed Mahameed
2023-06-02 19:12 ` [net-next V2 01/14] net/mlx5e: en_tc, Extend peer flows to a list Saeed Mahameed
2023-06-05 23:00   ` patchwork-bot+netdevbpf [this message]
2023-06-02 19:12 ` [net-next V2 02/14] net/mlx5e: tc, Refactor peer add/del flow Saeed Mahameed
2023-06-02 19:12 ` [net-next V2 03/14] net/mlx5e: rep, store send to vport rules per peer Saeed Mahameed
2023-06-02 19:12 ` [net-next V2 04/14] net/mlx5e: en_tc, re-factor query route port Saeed Mahameed
2023-06-02 19:12 ` [net-next V2 05/14] net/mlx5e: Handle offloads flows per peer Saeed Mahameed
2023-06-02 19:12 ` [net-next V2 06/14] net/mlx5: E-switch, enlarge peer miss group table Saeed Mahameed
2023-06-02 19:12 ` [net-next V2 07/14] net/mlx5: E-switch, refactor FDB miss rule add/remove Saeed Mahameed
2023-06-02 19:12 ` [net-next V2 08/14] net/mlx5: E-switch, Handle multiple master egress rules Saeed Mahameed
2023-06-02 19:12 ` [net-next V2 09/14] net/mlx5: E-switch, generalize shared FDB creation Saeed Mahameed
2023-06-02 19:12 ` [net-next V2 10/14] net/mlx5: DR, handle more than one peer domain Saeed Mahameed
2023-06-02 19:12 ` [net-next V2 11/14] net/mlx5: Devcom, Rename paired to ready Saeed Mahameed
2023-06-02 19:12 ` [net-next V2 12/14] net/mlx5: E-switch, mark devcom as not ready when all eswitches are unpaired Saeed Mahameed
2023-06-02 19:13 ` [net-next V2 13/14] net/mlx5: Devcom, introduce devcom_for_each_peer_entry Saeed Mahameed
2023-06-02 19:13 ` [net-next V2 14/14] net/mlx5: Devcom, extend mlx5_devcom_send_event to work with more than two devices Saeed Mahameed
2023-06-03  7:26 ` [pull request][net-next V2 00/14] mlx5 updates 2023-05-31 Simon Horman

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=168600602472.28052.8782299631686773162.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=roid@nvidia.com \
    --cc=saeed@kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=tariqt@nvidia.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.