public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: Doug Ledford <dledford@redhat.com>,
	Jason Gunthorpe <jgg@nvidia.com>,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH rdma-rc 1/2] RDMA/mlx5: Set correct kernel-doc identifier
Date: Tue, 2 Mar 2021 13:35:41 +0200	[thread overview]
Message-ID: <YD4jDbyn6PZQ76HB@unreal> (raw)
In-Reply-To: <20210302104410.GD2690909@dell>

On Tue, Mar 02, 2021 at 10:44:10AM +0000, Lee Jones wrote:
> On Tue, 02 Mar 2021, Leon Romanovsky wrote:
>
> > On Tue, Mar 02, 2021 at 09:31:09AM +0000, Lee Jones wrote:
> > > On Tue, 02 Mar 2021, Leon Romanovsky wrote:
> > >
> > > > From: Leon Romanovsky <leonro@nvidia.com>
> > > >
> > > > The W=1 allmodconfig build produces the following warning:
> > > > drivers/infiniband/hw/mlx5/odp.c:1086: warning: wrong kernel-doc identifier on line:
> > > >   * Parse a series of data segments for page fault handling.
> > > >
> > > > Fix it by changing /** to be /* as it is written in kernel-doc documentation.
> > > >
> > > > Fixes: 5e769e444d26 ("RDMA/hw/mlx5/odp: Fix formatting and add missing descriptions in 'pagefault_data_segments()'")
> > > > Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> > > > ---
> > > >  drivers/infiniband/hw/mlx5/odp.c | 2 +-
> > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --git a/drivers/infiniband/hw/mlx5/odp.c b/drivers/infiniband/hw/mlx5/odp.c
> > > > index 374698186662..b103555b1f5d 100644
> > > > --- a/drivers/infiniband/hw/mlx5/odp.c
> > > > +++ b/drivers/infiniband/hw/mlx5/odp.c
> > > > @@ -1082,7 +1082,7 @@ static int pagefault_single_data_segment(struct mlx5_ib_dev *dev,
> > > >  	return ret ? ret : npages;
> > > >  }
> > > >
> > > > -/**
> > > > +/*
> > >
> > > This is not the correct fix.
> >
> > I don't want kernel-doc comments on static function. It is local to this
> > file, so change from /** to /* was to mark that this is not kernel-doc.
> >
> > >
> > > Kernel-doc is asking for the function name.
> >
> > The thing is that I don't want it to be kernel-doc.
>
> In the past, if the authors have made a good effort to document the
> function, I have left the kernel-doc formatting in place.  It looks
> odd / non-consistent to demote some, but not others.  Especially
> considering there are 100's if not 1000's of other static functions
> documented in the kernel with kernel-doc formatting.

I'm not interested to solve all kernel-doc issues, but only specific to
drivers/infiniband and especially this mlx5 driver which is under my
responsibility.

>
> There are also 1000's of uses that are left referenced by kernel-doc::
> tags.  See: scripts/find-unused-docs.sh for more details.
>
> If you're going to go through with this, you should at least say what
> you're doing and why in the commit message.  Since demoting an
> otherwise full and complete kernel-doc header seems a little harsh to
> say the least.

It wasn't kernel-doc from the beginning.

Thanks

>
> --
> Lee Jones [李琼斯]
> Senior Technical Lead - Developer Services
> Linaro.org │ Open source software for Arm SoCs
> Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2021-03-02 17:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02  7:42 [PATCH rdma-rc 0/2] W=1 compilation fixes leftovers Leon Romanovsky
2021-03-02  7:42 ` [PATCH rdma-rc 1/2] RDMA/mlx5: Set correct kernel-doc identifier Leon Romanovsky
2021-03-02  9:31   ` Lee Jones
2021-03-02 10:26     ` Leon Romanovsky
2021-03-02 10:44       ` Lee Jones
2021-03-02 11:35         ` Leon Romanovsky [this message]
2021-03-02  7:42 ` [PATCH rdma-rc 2/2] RDMA/uverbs: Fix kernel-doc warning of _uverbs_alloc Leon Romanovsky
2021-03-02  9:32   ` Lee Jones
2021-03-02 10:26     ` Leon Romanovsky
2021-03-03 17:22 ` [PATCH rdma-rc 0/2] W=1 compilation fixes leftovers 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=YD4jDbyn6PZQ76HB@unreal \
    --to=leon@kernel.org \
    --cc=dledford@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --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