From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
Leon Romanovsky <leonro@nvidia.com>,
Avihai Horon <avihaih@nvidia.com>,
Bart Van Assche <bvanassche@acm.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
Jack Morgenstein <jackm@dev.mellanox.co.il>,
Leon Romanovsky <leonro@mellanox.com>,
<linux-kernel@vger.kernel.org>, <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH rdma-next 0/3] Various fixes collected over time
Date: Thu, 10 Dec 2020 16:26:00 -0400 [thread overview]
Message-ID: <20201210202600.GA2136131@nvidia.com> (raw)
In-Reply-To: <20201208073545.9723-1-leon@kernel.org>
On Tue, Dec 08, 2020 at 09:35:42AM +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Hi,
>
> This is set of various and unrelated fixes that we collected over time.
>
> Thanks
>
> Avihai Horon (1):
> RDMA/uverbs: Fix incorrect variable type
>
> Jack Morgenstein (2):
> RDMA/core: Clean up cq pool mechanism
> RDMA/core: Do not indicate device ready when device enablement fails
>
> drivers/infiniband/core/core_priv.h | 3 +--
> drivers/infiniband/core/cq.c | 12 ++----------
> drivers/infiniband/core/device.c | 16 ++++++++++------
> .../infiniband/core/uverbs_std_types_device.c | 14 +++++---------
> include/rdma/uverbs_ioctl.h | 10 ++++++++++
> 5 files changed, 28 insertions(+), 27 deletions(-)
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2020-12-10 20:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 7:35 [PATCH rdma-next 0/3] Various fixes collected over time Leon Romanovsky
2020-12-08 7:35 ` [PATCH rdma-next 1/3] RDMA/core: Clean up cq pool mechanism Leon Romanovsky
2020-12-08 7:35 ` [PATCH rdma-next 2/3] RDMA/core: Do not indicate device ready when device enablement fails Leon Romanovsky
2020-12-08 7:35 ` [PATCH rdma-next 3/3] RDMA/uverbs: Fix incorrect variable type Leon Romanovsky
2020-12-08 7:55 ` Dan Carpenter
2020-12-08 8:54 ` Leon Romanovsky
2020-12-08 9:26 ` Dan Carpenter
2020-12-08 14:00 ` Jason Gunthorpe
2020-12-10 20:26 ` 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=20201210202600.GA2136131@nvidia.com \
--to=jgg@nvidia.com \
--cc=avihaih@nvidia.com \
--cc=bvanassche@acm.org \
--cc=dan.carpenter@oracle.com \
--cc=dledford@redhat.com \
--cc=jackm@dev.mellanox.co.il \
--cc=leon@kernel.org \
--cc=leonro@mellanox.com \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).