public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH rdma-next 0/4] Mellanox ConnectX-3/ConnectX-4 fixes for 4.10
Date: Sun, 27 Nov 2016 15:18:18 +0200	[thread overview]
Message-ID: <1480252702-8005-1-git-send-email-leon@kernel.org> (raw)

Hi Doug,

Please find below four different fixes to ConnectX-3/ConnectX-4.

This patchset was generated against v4.9-rc6 and targeted for 4.10.

Available in the "topic/mlx-fixes-4.10" topic branch of this git repo:
git://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git

Or for browsing:
https://git.kernel.org/cgit/linux/kernel/git/leon/linux-rdma.git/log/?h=topic/mlx-fixes-4.10

Thanks

Eli Cohen (1):
  IB/mlx5: Avoid system crash when enabling many VFs

Jack Morgenstein (1):
  IB/mlx4: Fix out-of-range array index in destroy qp flow

Maor Gottlieb (2):
  IB/mlx5: Assign SRQ type earlier
  IB/mlx5: Use u64 for UMR length

 drivers/infiniband/hw/mlx4/qp.c      | 3 ++-
 drivers/infiniband/hw/mlx5/mlx5_ib.h | 2 +-
 drivers/infiniband/hw/mlx5/mr.c      | 3 ++-
 drivers/infiniband/hw/mlx5/srq.c     | 2 +-
 4 files changed, 6 insertions(+), 4 deletions(-)

--
2.7.4

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2016-11-27 13:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-27 13:18 Leon Romanovsky [this message]
     [not found] ` <1480252702-8005-1-git-send-email-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-11-27 13:18   ` [PATCH rdma-next 1/4] IB/mlx4: Fix out-of-range array index in destroy qp flow Leon Romanovsky
2016-11-27 16:56     ` Bart Van Assche
     [not found]       ` <BLUPR02MB1683B2E832867815771A4B2C818B0-Y8PPn9RqzNfZ9ihocuPUdanrV9Ap65cLvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2016-11-28  8:31         ` Leon Romanovsky
     [not found]           ` <20161128083107.GB6380-2ukJVAZIZ/Y@public.gmane.org>
2016-11-28 16:29             ` Bart Van Assche
     [not found]               ` <bdd9788e-d393-b23e-876c-ae84774fdccd-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2016-12-01  5:31                 ` Leon Romanovsky
2016-12-01  5:35                   ` Bart Van Assche
     [not found]                     ` <BLUPR02MB16836D6466A901D088E1FE65818F0-Y8PPn9RqzNfZ9ihocuPUdanrV9Ap65cLvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2016-12-01  7:02                       ` Leon Romanovsky
2016-11-27 13:18   ` [PATCH rdma-next 2/4] IB/mlx5: Assign SRQ type earlier Leon Romanovsky
2016-11-27 13:18   ` [PATCH rdma-next 3/4] IB/mlx5: Avoid system crash when enabling many VFs Leon Romanovsky
2016-11-27 13:18   ` [PATCH rdma-next 4/4] IB/mlx5: Use u64 for UMR length Leon Romanovsky
2016-12-14 19:05   ` [PATCH rdma-next 0/4] Mellanox ConnectX-3/ConnectX-4 fixes for 4.10 Doug Ledford

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=1480252702-8005-1-git-send-email-leon@kernel.org \
    --to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox