All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
	Maor Gottlieb <maorg@nvidia.com>,
	Daria Velikovsky <daria@mellanox.com>,
	linux-rdma@vger.kernel.org, Mark Bloch <markb@nvidia.com>
Subject: Re: [PATCH rdma-next] RDMA/mlx5: Fix drop packet rule in egress table
Date: Fri, 26 Mar 2021 13:58:24 -0300	[thread overview]
Message-ID: <20210326165824.GB863945@nvidia.com> (raw)
In-Reply-To: <20210318135123.680759-1-leon@kernel.org>

On Thu, Mar 18, 2021 at 03:51:23PM +0200, Leon Romanovsky wrote:
> From: Maor Gottlieb <maorg@nvidia.com>
> 
> Initial drop action support missed that drop action can be added to
> egress flow tables as well. Add the missing support.
> 
> This requires making sure that dest_type isn't set to PORT which in
> turn exposes a possibility of passing dst while indicating number of
> dsts as zero. Explicitly check for number of dsts and pass the appropriate
> pointer.
> 
> Fixes: f29de9eee782 ("RDMA/mlx5: Add support for drop action in DV steering")
> Reviewed-by: Mark Bloch <markb@nvidia.com>
> Signed-off-by: Maor Gottlieb <maorg@nvidia.com>
> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> ---
>  drivers/infiniband/hw/mlx5/fs.c | 9 +++++----
>  1 file changed, 5 insertions(+), 4 deletions(-)

Applied to for-next, thanks

Jason

      reply	other threads:[~2021-03-26 16:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 13:51 [PATCH rdma-next] RDMA/mlx5: Fix drop packet rule in egress table Leon Romanovsky
2021-03-26 16:58 ` Jason Gunthorpe [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=20210326165824.GB863945@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=daria@mellanox.com \
    --cc=dledford@redhat.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=maorg@nvidia.com \
    --cc=markb@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.