From: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
To: Leon Romanovsky <leon@kernel.org>,
Doug Ledford <dledford@redhat.com>,
Jason Gunthorpe <jgg@nvidia.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
Jack Wang <jinpu.wang@ionos.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Max Gurtovoy <mgurtovoy@nvidia.com>,
"Md. Haris Iqbal" <haris.iqbal@ionos.com>,
Mike Marciniszyn <mike.marciniszyn@cornelisnetworks.com>,
Sagi Grimberg <sagi@grimberg.me>,
target-devel@vger.kernel.org
Subject: Re: [PATCH rdma-next v1] RDMA: Fix kernel-doc warnings about wrong comment
Date: Thu, 3 Jun 2021 11:15:45 -0400 [thread overview]
Message-ID: <bf541aa7-db6a-e553-5a9d-a95d19440520@cornelisnetworks.com> (raw)
In-Reply-To: <8b40bbff098247962af5a7b35d47b2e964daa523.1622726066.git.leonro@nvidia.com>
On 6/3/21 9:16 AM, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Compilation with W=1 produces warnings similar to the below.
>
> drivers/infiniband/ulp/ipoib/ipoib_main.c:320: warning: This comment
> starts with '/**', but isn't a kernel-doc comment. Refer
> Documentation/doc-guide/kernel-doc.rst
>
> All such occurrences were found with the following one line
> git grep -A 1 "\/\*\*" drivers/infiniband/
>
> Reviewed-by: Jack Wang <jinpu.wang@ionos.com> #rtrs
> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Thanks for doing this.
Reviewed-by: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
next prev parent reply other threads:[~2021-06-03 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 13:16 [PATCH rdma-next v1] RDMA: Fix kernel-doc warnings about wrong comment Leon Romanovsky
2021-06-03 15:15 ` Dennis Dalessandro [this message]
2021-06-12 6:34 ` 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=bf541aa7-db6a-e553-5a9d-a95d19440520@cornelisnetworks.com \
--to=dennis.dalessandro@cornelisnetworks.com \
--cc=dledford@redhat.com \
--cc=haris.iqbal@ionos.com \
--cc=jgg@nvidia.com \
--cc=jinpu.wang@ionos.com \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mgurtovoy@nvidia.com \
--cc=mike.marciniszyn@cornelisnetworks.com \
--cc=sagi@grimberg.me \
--cc=target-devel@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).