All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@mellanox.com>
Cc: Leon Romanovsky <leonro@mellanox.com>,
	linux-rdma@vger.kernel.org, Mark Zhang <markz@mellanox.com>
Subject: [PATCH rdma-next 0/3] mlx5 ECE fixes DC ECE code
Date: Tue,  2 Jun 2020 15:55:45 +0300	[thread overview]
Message-ID: <20200602125548.172654-1-leon@kernel.org> (raw)

From: Leon Romanovsky <leonro@mellanox.com>

Hi,

This are three patches which I would ask to consider for current PR
to Linus.

First two patches are fixing corner cases that are not possible
in the real life and the third patch is needed to ensure that API
toward user space is feature complete and won't need any extra
ucontext flags.

The code of third patch was already presented in v0 and v1,
but was dropped later.

Leon Romanovsky (3):
  RDMA/mlx5: Return an error if copy_to_user fails
  RDMA/mlx5: Don't rely on FW to set zeros in ECE response
  RDMA/mlx5: Return ECE DC support

 drivers/infiniband/hw/mlx5/qp.c | 59 +++++++++++++++++++++------------
 include/linux/mlx5/mlx5_ifc.h   |  5 +--
 2 files changed, 40 insertions(+), 24 deletions(-)

--
2.26.2


             reply	other threads:[~2020-06-02 12:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02 12:55 Leon Romanovsky [this message]
2020-06-02 12:55 ` [PATCH rdma-next 1/3] RDMA/mlx5: Return an error if copy_to_user fails Leon Romanovsky
2020-06-02 12:55 ` [PATCH rdma-next 2/3] RDMA/mlx5: Don't rely on FW to set zeros in ECE response Leon Romanovsky
2020-06-02 12:55 ` [PATCH mlx5-next 3/3] RDMA/mlx5: Return ECE DC support Leon Romanovsky
2020-06-03 18:48 ` [PATCH rdma-next 0/3] mlx5 ECE fixes DC ECE code 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=20200602125548.172654-1-leon@kernel.org \
    --to=leon@kernel.org \
    --cc=dledford@redhat.com \
    --cc=jgg@mellanox.com \
    --cc=leonro@mellanox.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=markz@mellanox.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.