From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
Leon Romanovsky <leonro@nvidia.com>,
Krishna Kumar <krkumar2@in.ibm.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Parav Pandit <parav@nvidia.com>,
Sean Hefty <sean.hefty@intel.com>, Shay Drory <shayd@nvidia.com>
Subject: Re: [PATCH rdma-next 0/3] CMA fixes
Date: Wed, 21 Apr 2021 20:59:09 -0300 [thread overview]
Message-ID: <20210421235909.GA2329448@nvidia.com> (raw)
In-Reply-To: <cover.1618753862.git.leonro@nvidia.com>
On Sun, Apr 18, 2021 at 04:55:51PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Another round of fixes to cma.c
>
> Parav Pandit (1):
> RDMA/cma: Skip device which doesn't support CM
>
> Shay Drory (2):
> RDMA/core: Add CM to restrack after successful attachment to a device
These two applied to for-next
> RDMA/core: Fix check of device in rdma_listen()
Lets think about this one some more
Thanks,
Jason
next prev parent reply other threads:[~2021-04-21 23:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 13:55 [PATCH rdma-next 0/3] CMA fixes Leon Romanovsky
2021-04-18 13:55 ` [PATCH rdma-next 1/3] RDMA/cma: Skip device which doesn't support CM Leon Romanovsky
2021-04-18 13:55 ` [PATCH rdma-next 2/3] RDMA/core: Fix check of device in rdma_listen() Leon Romanovsky
2021-04-22 11:28 ` Jason Gunthorpe
2021-04-22 12:44 ` Shay Drory
2021-04-22 12:51 ` Jason Gunthorpe
2021-04-22 13:01 ` Leon Romanovsky
2021-04-22 13:02 ` Jason Gunthorpe
2021-04-22 14:58 ` Leon Romanovsky
2021-04-22 16:18 ` Jason Gunthorpe
2021-04-25 13:17 ` Leon Romanovsky
2021-04-18 13:55 ` [PATCH rdma-next 3/3] RDMA/core: Add CM to restrack after successful attachment to a device Leon Romanovsky
2021-04-21 23:59 ` Jason Gunthorpe [this message]
2021-04-22 6:46 ` [PATCH rdma-next 0/3] CMA fixes Leon Romanovsky
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=20210421235909.GA2329448@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=krkumar2@in.ibm.com \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=sean.hefty@intel.com \
--cc=shayd@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 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).