From: Jason Gunthorpe <jgg@nvidia.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: "Linux Doc Mailing List" <linux-doc@vger.kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
"Håkon Bugge" <haakon.bugge@oracle.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Bart Van Assche" <bvanassche@acm.org>,
"Chuck Lever" <chuck.lever@oracle.com>,
"Danit Goldberg" <danitg@mellanox.com>,
"Dennis Dalessandro" <dennis.dalessandro@cornelisnetworks.com>,
"Divya Indi" <divya.indi@oracle.com>,
"Doug Ledford" <dledford@redhat.com>,
"Gal Pressman" <galpress@amazon.com>,
"Leon Romanovsky" <leon@kernel.org>,
"Maor Gottlieb" <maorg@mellanox.com>,
"Max Gurtovoy" <mgurtovoy@nvidia.com>,
"Mike Marciniszyn" <mike.marciniszyn@cornelisnetworks.com>,
"Moni Shoua" <monis@mellanox.com>,
"Or Gerlitz" <ogerlitz@mellanox.com>,
"Parav Pandit" <parav@mellanox.com>,
"Sagi Grimberg" <sagi@grimberg.me>,
"Ursula Braun" <ubraun@linux.ibm.com>,
"Xi Wang" <wangxi11@huawei.com>,
"Yamin Friedman" <yaminf@mellanox.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
target-devel@vger.kernel.org
Subject: Re: [PATCH v4 07/27] IB: fix kernel-doc markups
Date: Mon, 23 Nov 2020 19:45:42 -0400 [thread overview]
Message-ID: <20201123234542.GA142861@nvidia.com> (raw)
In-Reply-To: <4983a0c6fe5dbc2c779d2b5950a6f90f81a16d56.1605521731.git.mchehab+huawei@kernel.org>
On Mon, Nov 16, 2020 at 11:18:03AM +0100, Mauro Carvalho Chehab wrote:
> +/**
> + * ib_alloc_pd - Allocates an unused protection domain.
> + * @device: The device on which to allocate the protection domain.
> + * @flags: protection domain flags
> + *
> + * A protection domain object provides an association between QPs, shared
> + * receive queues, address handles, memory regions, and memory windows.
> + *
> + * Every PD has a local_dma_lkey which can be used as the lkey value for local
> + * memory operations.
> + */
> #define ib_alloc_pd(device, flags) \
> __ib_alloc_pd((device), (flags), KBUILD_MODNAME)
Why this hunk adding a completely new description in this patch?
Jason
next prev parent reply other threads:[~2020-11-23 23:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 10:17 [PATCH v4 00/27]Fix several bad kernel-doc markups Mauro Carvalho Chehab
2020-11-16 10:18 ` [PATCH v4 07/27] IB: fix " Mauro Carvalho Chehab
2020-11-16 10:36 ` Gustavo A. R. Silva
2020-11-23 23:45 ` Jason Gunthorpe [this message]
2020-12-01 11:39 ` Mauro Carvalho Chehab
2020-11-17 22:19 ` [PATCH v4 00/27]Fix several bad " Jakub Kicinski
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=20201123234542.GA142861@nvidia.com \
--to=jgg@nvidia.com \
--cc=bvanassche@acm.org \
--cc=chuck.lever@oracle.com \
--cc=corbet@lwn.net \
--cc=danitg@mellanox.com \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=divya.indi@oracle.com \
--cc=dledford@redhat.com \
--cc=galpress@amazon.com \
--cc=gustavoars@kernel.org \
--cc=haakon.bugge@oracle.com \
--cc=leon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=maorg@mellanox.com \
--cc=mchehab+huawei@kernel.org \
--cc=mgurtovoy@nvidia.com \
--cc=mike.marciniszyn@cornelisnetworks.com \
--cc=monis@mellanox.com \
--cc=ogerlitz@mellanox.com \
--cc=parav@mellanox.com \
--cc=sagi@grimberg.me \
--cc=target-devel@vger.kernel.org \
--cc=ubraun@linux.ibm.com \
--cc=wangxi11@huawei.com \
--cc=yaminf@mellanox.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).