From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] remoteproc: Fix various kernel-doc warnings
Date: Thu, 27 May 2021 22:07:20 -0500 [thread overview]
Message-ID: <YLBeaE8IWlmDjHaY@builder.lan> (raw)
In-Reply-To: <20210525180006.GD1113058@xps15>
On Tue 25 May 13:00 CDT 2021, Mathieu Poirier wrote:
> On Wed, May 19, 2021 at 01:03:04PM -0500, Suman Anna wrote:
> > diff --git a/drivers/remoteproc/remoteproc_elf_loader.c b/drivers/remoteproc/remoteproc_elf_loader.c
[..]
> > @@ -362,7 +366,7 @@ EXPORT_SYMBOL(rproc_elf_load_rsc_table);
> > * This function finds the location of the loaded resource table. Don't
> > * call this function if the table wasn't loaded yet - it's a bug if you do.
> > *
> > - * Returns the pointer to the resource table if it is found or NULL otherwise.
> > + * Return: pointer to the resource table if it is found or NULL otherwise.
>
> Here the '.' has been kept while it was remove for all of the above. I don't
> know that the right guidelines are for this.
>
Reviewing https://www.kernel.org/doc/html/latest/doc-guide/kernel-doc.html
I don't see that this is defined. So I'm fine with whatever looks good.
That said, the section about "Return values" shows that the "Return:
..." line should be short and concise and if needed followed by a
newline and then a longer paragraph.
I'll fix the capitalization of "the" below and apply this as is and we
can go back an reformat these multiline Return entries later...
> > * If the table wasn't loaded yet the result is unspecified.
> > */
[..]
> > diff --git a/include/linux/remoteproc.h b/include/linux/remoteproc.h
[..]
> > + * 2. immediately following this structure is the virtio config space for
> > + * this vdev (which is specific to the vdev; for more info, read the virtio
> > + * spec). the size of the config space is specified by @config_len.
>
> s/the/The
>
[..]
> > struct rproc {
> > @@ -613,10 +617,10 @@ struct rproc_vring {
> > * struct rproc_vdev - remoteproc state for a supported virtio device
> > * @refcount: reference counter for the vdev and vring allocations
> > * @subdev: handle for registering the vdev as a rproc subdevice
> > + * @dev: device struct used for reference count semantics
> > * @id: virtio device id (as in virtio_ids.h)
> > * @node: list node
> > * @rproc: the rproc handle
> > - * @vdev: the virio device
> > * @vring: the vrings for this vdev
> > * @rsc_offset: offset of the vdev's resource entry
> > * @index: vdev position versus other vdev declared in resource table
>
> With or without the above:
>
> Reviewed-by: Mathieu Poirier <mathieu.poirier@linaro.org>
>
Thanks Mathieu, and thanks Suman.
Regards,
Bjorn
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-05-28 3:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 18:03 [PATCH 0/2] Minor remoteproc cleanups Suman Anna
2021-05-19 18:03 ` [PATCH 1/2] remoteproc: Add kernel-doc comment for is_iomem Suman Anna
2021-05-25 17:37 ` Mathieu Poirier
2021-05-19 18:03 ` [PATCH 2/2] remoteproc: Fix various kernel-doc warnings Suman Anna
2021-05-25 18:00 ` Mathieu Poirier
2021-05-25 18:07 ` Suman Anna
2021-05-28 3:07 ` Bjorn Andersson [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=YLBeaE8IWlmDjHaY@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.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).