From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
Leon Romanovsky <leonro@nvidia.com>, <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH rdma-next v4 0/5] Track memory allocation with restrack DB help (Part I)
Date: Thu, 12 Nov 2020 14:59:51 -0400 [thread overview]
Message-ID: <20201112185951.GA981682@nvidia.com> (raw)
In-Reply-To: <20201104144008.3808124-1-leon@kernel.org>
On Wed, Nov 04, 2020 at 04:40:03PM +0200, Leon Romanovsky wrote:
> Leon Romanovsky (5):
> RDMA/core: Allow drivers to disable restrack DB
This stuff is never used
> RDMA/cma: Be strict with attaching to CMA device
This adds a return 0 which is pointless..
> RDMA/counter: Combine allocation and bind logic
> RDMA/restrack: Store all special QPs in restrack DB
> RDMA/cma: Add missing error handling of listen_id
Took these three to for-next
Thanks,
Jason
next prev parent reply other threads:[~2020-11-12 18:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 14:40 [PATCH rdma-next v4 0/5] Track memory allocation with restrack DB help (Part I) Leon Romanovsky
2020-11-04 14:40 ` [PATCH rdma-next v4 1/5] RDMA/core: Allow drivers to disable restrack DB Leon Romanovsky
2020-11-04 14:40 ` [PATCH rdma-next v4 2/5] RDMA/counter: Combine allocation and bind logic Leon Romanovsky
2020-11-04 14:40 ` [PATCH rdma-next v4 3/5] RDMA/restrack: Store all special QPs in restrack DB Leon Romanovsky
2020-11-04 14:40 ` [PATCH rdma-next v4 4/5] RDMA/cma: Add missing error handling of listen_id Leon Romanovsky
2020-11-04 14:40 ` [PATCH rdma-next v4 5/5] RDMA/cma: Be strict with attaching to CMA device Leon Romanovsky
2020-11-12 18:59 ` Jason Gunthorpe [this message]
2020-11-12 19:23 ` [PATCH rdma-next v4 0/5] Track memory allocation with restrack DB help (Part I) Leon Romanovsky
2020-11-12 19:48 ` 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=20201112185951.GA981682@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--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 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.