From: Leon Romanovsky <leonro@nvidia.com>
To: Saeed Mahameed <saeed@kernel.org>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
Jason Gunthorpe <jgg@nvidia.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>, <netdev@vger.kernel.org>,
<linux-rdma@vger.kernel.org>, Maor Gottlieb <maorg@nvidia.com>,
Mark Bloch <mbloch@nvidia.com>
Subject: Re: [PATCH mlx5-next 2/4] net/mlx5: Refactor mlx5_get_flow_namespace
Date: Thu, 2 Dec 2021 16:58:21 +0200 [thread overview]
Message-ID: <YajfDXE4zJiOxIqz@unreal> (raw)
In-Reply-To: <20211201193621.9129-3-saeed@kernel.org>
On Wed, Dec 01, 2021 at 11:36:19AM -0800, Saeed Mahameed wrote:
> From: Maor Gottlieb <maorg@nvidia.com>
>
> Have all the namespace type check in the same switch case.
>
> Signed-off-by: Maor Gottlieb <maorg@nvidia.com>
> Reviewed-by: Mark Bloch <mbloch@nvidia.com>
> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
> ---
> .../net/ethernet/mellanox/mlx5/core/fs_core.c | 44 ++++++++++++++-----
> 1 file changed, 32 insertions(+), 12 deletions(-)
>
Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
next prev parent reply other threads:[~2021-12-02 14:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 19:36 [PATCH mlx5-next 0/4] Add support to multiple RDMA priorities for FDB rules Saeed Mahameed
2021-12-01 19:36 ` [PATCH mlx5-next 1/4] net/mlx5: Separate FDB namespace Saeed Mahameed
2021-12-02 14:58 ` Leon Romanovsky
2021-12-01 19:36 ` [PATCH mlx5-next 2/4] net/mlx5: Refactor mlx5_get_flow_namespace Saeed Mahameed
2021-12-02 14:58 ` Leon Romanovsky [this message]
2021-12-01 19:36 ` [PATCH mlx5-next 3/4] net/mlx5: Create more priorities for FDB bypass namespace Saeed Mahameed
2021-12-02 14:58 ` Leon Romanovsky
2021-12-01 19:36 ` [PATCH mlx5-next 4/4] RDMA/mlx5: Add support to multiple priorities for FDB rules Saeed Mahameed
2021-12-02 14:58 ` Leon Romanovsky
2021-12-07 18:58 ` [PATCH mlx5-next 0/4] Add support to multiple RDMA " Jason Gunthorpe
2021-12-14 0:04 ` Saeed Mahameed
2021-12-15 12:31 ` Jason Gunthorpe
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=YajfDXE4zJiOxIqz@unreal \
--to=leonro@nvidia.com \
--cc=davem@davemloft.net \
--cc=jgg@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=maorg@nvidia.com \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=saeed@kernel.org \
--cc=saeedm@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.