From: Jason Gunthorpe <jgg@nvidia.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: "Linux Doc Mailing List" <linux-doc@vger.kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
"Håkon Bugge" <haakon.bugge@oracle.com>,
"Bart Van Assche" <bvanassche@acm.org>,
"Chuck Lever" <chuck.lever@oracle.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>,
"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 v5 02/16] IB: fix kernel-doc markups
Date: Mon, 7 Dec 2020 15:46:01 -0400 [thread overview]
Message-ID: <20201207194601.GB1773945@nvidia.com> (raw)
In-Reply-To: <78b98c41a5a0f4c0106433d305b143028a4168b0.1606823973.git.mchehab+huawei@kernel.org>
On Tue, Dec 01, 2020 at 01:08:55PM +0100, Mauro Carvalho Chehab wrote:
> Some functions have different names between their prototypes
> and the kernel-doc markup.
>
> Others need to be fixed, as kernel-doc markups should use this format:
> identifier - description
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
> drivers/infiniband/core/cm.c | 5 +++--
> drivers/infiniband/core/cq.c | 4 ++--
> drivers/infiniband/core/iwpm_util.h | 2 +-
> drivers/infiniband/core/sa_query.c | 3 ++-
> drivers/infiniband/core/verbs.c | 4 ++--
> drivers/infiniband/sw/rdmavt/ah.c | 2 +-
> drivers/infiniband/sw/rdmavt/mcast.c | 12 ++++++------
> drivers/infiniband/sw/rdmavt/qp.c | 8 ++++----
> drivers/infiniband/ulp/iser/iscsi_iser.c | 2 +-
> drivers/infiniband/ulp/opa_vnic/opa_vnic_encap.h | 2 +-
> .../infiniband/ulp/opa_vnic/opa_vnic_vema_iface.c | 2 +-
> drivers/infiniband/ulp/srpt/ib_srpt.h | 2 +-
> include/rdma/ib_verbs.h | 11 +++++++++++
> 13 files changed, 36 insertions(+), 23 deletions(-)
I've taken this to the RDMA tree, thanks
Jason
prev parent reply other threads:[~2020-12-07 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 12:08 [PATCH v5 00/16]Fix several bad kernel-doc markups Mauro Carvalho Chehab
2020-12-01 12:08 ` [PATCH v5 02/16] IB: fix " Mauro Carvalho Chehab
2020-12-07 19:46 ` 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=20201207194601.GB1773945@nvidia.com \
--to=jgg@nvidia.com \
--cc=bvanassche@acm.org \
--cc=chuck.lever@oracle.com \
--cc=corbet@lwn.net \
--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=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).