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, vladbu@nvidia.com, maord@nvidia.com,
	roid@nvidia.com
Subject: Re: [net-next 01/15] net/mlx5: Add mlx5_ifc definitions for bridge multicast support
Date: Fri, 14 Apr 2023 05:30:22 +0000	[thread overview]
Message-ID: <168145022238.29714.3408827760407301679.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230412040752.14220-2-saeed@kernel.org>

Hello:

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

On Tue, 11 Apr 2023 21:07:38 -0700 you wrote:
> From: Vlad Buslov <vladbu@nvidia.com>
> 
> Add the required hardware definitions to mlx5_ifc: fdb_uplink_hairpin,
> fdb_multi_path_any_table_limit_regc, fdb_multi_path_any_table.
> 
> Signed-off-by: Vlad Buslov <vladbu@nvidia.com>
> Reviewed-by: Maor Dickman <maord@nvidia.com>
> Reviewed-by: Roi Dayan <roid@nvidia.com>
> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
> 
> [...]

Here is the summary with links:
  - [net-next,01/15] net/mlx5: Add mlx5_ifc definitions for bridge multicast support
    https://git.kernel.org/netdev/net-next/c/e5688f6fb9e3
  - [net-next,02/15] net/mlx5: Bridge, increase bridge tables sizes
    https://git.kernel.org/netdev/net-next/c/9071b423c302
  - [net-next,03/15] net/mlx5: Bridge, move additional data structures to priv header
    https://git.kernel.org/netdev/net-next/c/6767c97d7adc
  - [net-next,04/15] net/mlx5: Bridge, extract code to lookup parent bridge of port
    https://git.kernel.org/netdev/net-next/c/b99c4ef29e27
  - [net-next,05/15] net/mlx5: Bridge, snoop igmp/mld packets
    https://git.kernel.org/netdev/net-next/c/18c2916cee12
  - [net-next,06/15] net/mlx5: Bridge, add per-port multicast replication tables
    https://git.kernel.org/netdev/net-next/c/272ecfc92f6f
  - [net-next,07/15] net/mlx5: Bridge, support multicast VLAN pop
    https://git.kernel.org/netdev/net-next/c/b5e80625d168
  - [net-next,08/15] net/mlx5: Bridge, implement mdb offload
    https://git.kernel.org/netdev/net-next/c/70f0302b3f20
  - [net-next,09/15] net/mlx5: Bridge, add tracepoints for multicast
    https://git.kernel.org/netdev/net-next/c/55f3e740f7f6
  - [net-next,10/15] net/mlx5: Create a new profile for SFs
    https://git.kernel.org/netdev/net-next/c/9df839a711ae
  - [net-next,11/15] net/mlx5: DR, Set counter ID on the last STE for STEv1 TX
    https://git.kernel.org/netdev/net-next/c/cee6484eddc1
  - [net-next,12/15] net/mlx5: Add mlx5_ifc bits for modify header argument
    https://git.kernel.org/netdev/net-next/c/9fa7f1de3dda
  - [net-next,13/15] net/mlx5: Add new WQE for updating flow table
    https://git.kernel.org/netdev/net-next/c/977c4a3e7c89
  - [net-next,14/15] net/mlx5: DR, Prepare sending new WQE type
    https://git.kernel.org/netdev/net-next/c/1e5cc7369bb0
  - [net-next,15/15] net/mlx5: DR, Add modify-header-pattern ICM pool
    https://git.kernel.org/netdev/net-next/c/108ff8215b55

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



  reply	other threads:[~2023-04-14  5:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12  4:07 [pull request][net-next 00/15] mlx5 updates 2023-04-11 Saeed Mahameed
2023-04-12  4:07 ` [net-next 01/15] net/mlx5: Add mlx5_ifc definitions for bridge multicast support Saeed Mahameed
2023-04-14  5:30   ` patchwork-bot+netdevbpf [this message]
2023-04-12  4:07 ` [net-next 02/15] net/mlx5: Bridge, increase bridge tables sizes Saeed Mahameed
2023-04-12  4:07 ` [net-next 03/15] net/mlx5: Bridge, move additional data structures to priv header Saeed Mahameed
2023-04-12  4:07 ` [net-next 04/15] net/mlx5: Bridge, extract code to lookup parent bridge of port Saeed Mahameed
2023-04-12  4:07 ` [net-next 05/15] net/mlx5: Bridge, snoop igmp/mld packets Saeed Mahameed
2023-04-12  4:07 ` [net-next 06/15] net/mlx5: Bridge, add per-port multicast replication tables Saeed Mahameed
2023-04-12  4:07 ` [net-next 07/15] net/mlx5: Bridge, support multicast VLAN pop Saeed Mahameed
2023-04-12  4:07 ` [net-next 08/15] net/mlx5: Bridge, implement mdb offload Saeed Mahameed
2023-04-12  4:07 ` [net-next 09/15] net/mlx5: Bridge, add tracepoints for multicast Saeed Mahameed
2023-04-12  4:07 ` [net-next 10/15] net/mlx5: Create a new profile for SFs Saeed Mahameed
2023-04-12  4:07 ` [net-next 11/15] net/mlx5: DR, Set counter ID on the last STE for STEv1 TX Saeed Mahameed
2023-04-12  4:07 ` [net-next 12/15] net/mlx5: Add mlx5_ifc bits for modify header argument Saeed Mahameed
2023-04-12  4:07 ` [net-next 13/15] net/mlx5: Add new WQE for updating flow table Saeed Mahameed
2023-04-12  4:07 ` [net-next 14/15] net/mlx5: DR, Prepare sending new WQE type Saeed Mahameed
2023-04-12  4:07 ` [net-next 15/15] net/mlx5: DR, Add modify-header-pattern ICM pool Saeed Mahameed
2023-04-13  0:16 ` [pull request][net-next 00/15] mlx5 updates 2023-04-11 Jacob Keller

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=168145022238.29714.3408827760407301679.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=maord@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 \
    --cc=vladbu@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.