From: Jason Gunthorpe <jgg@ziepe.ca>
To: Danit Goldberg <danitg@mellanox.com>
Cc: linux-rdma@vger.kernel.org, leonro@mellanox.com
Subject: Re: [PATCH rdma-next] RDMA/cm: Use refcount_t type for refcount variable
Date: Tue, 19 Nov 2019 16:14:53 -0400 [thread overview]
Message-ID: <20191119201453.GA6338@ziepe.ca> (raw)
In-Reply-To: <1573997601-4502-1-git-send-email-danitg@mellanox.com>
On Sun, Nov 17, 2019 at 03:33:21PM +0200, Danit Goldberg wrote:
> The refcount_t API is a kernel self-protection mechanism, and therefore
> more suitable for counters variables.
>
> This patch replaces the counting API from atomic_t API to refcount_t API
> of the 'refcount' variable in cm_id_private struct.
>
> Signed-off-by: Danit Goldberg <danitg@mellanox.com>
> Reviewed-by: Leon Romanovsky <leonro@mellanox.com>
> ---
> drivers/infiniband/core/cm.c | 24 ++++++++++++------------
> 1 file changed, 12 insertions(+), 12 deletions(-)
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2019-11-19 20:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 13:33 [PATCH rdma-next] RDMA/cm: Use refcount_t type for refcount variable Danit Goldberg
2019-11-19 20:14 ` 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=20191119201453.GA6338@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=danitg@mellanox.com \
--cc=leonro@mellanox.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 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).