From: Jason Wang <jasowang@redhat.com>
To: Parav Pandit <parav@nvidia.com>,
virtualization@lists.linux-foundation.org
Cc: elic@nvidia.com, mst@redhat.com
Subject: Re: [PATCH linux-next v2 02/14] vdpa: Follow kdoc comment style
Date: Wed, 7 Apr 2021 11:09:57 +0800 [thread overview]
Message-ID: <ee143a65-a1ec-ae4f-4ad6-61d8797ae877@redhat.com> (raw)
In-Reply-To: <20210406170457.98481-3-parav@nvidia.com>
在 2021/4/7 上午1:04, Parav Pandit 写道:
> Follow comment style mentioned in the Writing kernel-doc document [1].
>
> Following warnings are fixed.
>
> $ scripts/kernel-doc -v -none drivers/vdpa/vdpa.c
> drivers/vdpa/vdpa.c:67: info: Scanning doc for __vdpa_alloc_device
> drivers/vdpa/vdpa.c:84: warning: No description found for return value of '__vdpa_alloc_device'
> drivers/vdpa/vdpa.c:153: info: Scanning doc for _vdpa_register_device
> drivers/vdpa/vdpa.c:163: warning: No description found for return value of '_vdpa_register_device'
> drivers/vdpa/vdpa.c:172: info: Scanning doc for vdpa_register_device
> drivers/vdpa/vdpa.c:180: warning: No description found for return value of 'vdpa_register_device'
> drivers/vdpa/vdpa.c:191: info: Scanning doc for _vdpa_unregister_device
> drivers/vdpa/vdpa.c:205: info: Scanning doc for vdpa_unregister_device
> drivers/vdpa/vdpa.c:217: info: Scanning doc for __vdpa_register_driver
> drivers/vdpa/vdpa.c:224: warning: No description found for return value of '__vdpa_register_driver'
> drivers/vdpa/vdpa.c:233: info: Scanning doc for vdpa_unregister_driver
> drivers/vdpa/vdpa.c:243: info: Scanning doc for vdpa_mgmtdev_register
> drivers/vdpa/vdpa.c:250: warning: No description found for return value of 'vdpa_mgmtdev_register'
>
> After the fix:
>
> scripts/kernel-doc -v -none drivers/vdpa/vdpa.c
> drivers/vdpa/vdpa.c:67: info: Scanning doc for __vdpa_alloc_device
> drivers/vdpa/vdpa.c:153: info: Scanning doc for _vdpa_register_device
> drivers/vdpa/vdpa.c:172: info: Scanning doc for vdpa_register_device
> drivers/vdpa/vdpa.c:191: info: Scanning doc for _vdpa_unregister_device
> drivers/vdpa/vdpa.c:205: info: Scanning doc for vdpa_unregister_device
> drivers/vdpa/vdpa.c:217: info: Scanning doc for __vdpa_register_driver
> drivers/vdpa/vdpa.c:233: info: Scanning doc for vdpa_unregister_driver
> drivers/vdpa/vdpa.c:243: info: Scanning doc for vdpa_mgmtdev_register
>
> [1] https://www.kernel.org/doc/html/latest/doc-guide/kernel-doc.html
>
> Signed-off-by: Parav Pandit <parav@nvidia.com>
> Reviewed-by: Eli Cohen <elic@nvidia.com>
Acked-by: Jason Wang <jasowang@redhat.com>
> ---
> drivers/vdpa/vdpa.c | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/vdpa/vdpa.c b/drivers/vdpa/vdpa.c
> index 5cffce67cab0..bb3f1d1f0422 100644
> --- a/drivers/vdpa/vdpa.c
> +++ b/drivers/vdpa/vdpa.c
> @@ -75,8 +75,8 @@ static void vdpa_release_dev(struct device *d)
> * Driver should use vdpa_alloc_device() wrapper macro instead of
> * using this directly.
> *
> - * Returns an error when parent/config/dma_dev is not set or fail to get
> - * ida.
> + * Return: Returns an error when parent/config/dma_dev is not set or fail to get
> + * ida.
> */
> struct vdpa_device *__vdpa_alloc_device(struct device *parent,
> const struct vdpa_config_ops *config,
> @@ -157,7 +157,7 @@ static int __vdpa_register_device(struct vdpa_device *vdev, int nvqs)
> * @vdev: the vdpa device to be registered to vDPA bus
> * @nvqs: number of virtqueues supported by this device
> *
> - * Returns an error when fail to add device to vDPA bus
> + * Return: Returns an error when fail to add device to vDPA bus
> */
> int _vdpa_register_device(struct vdpa_device *vdev, int nvqs)
> {
> @@ -174,7 +174,7 @@ EXPORT_SYMBOL_GPL(_vdpa_register_device);
> * @vdev: the vdpa device to be registered to vDPA bus
> * @nvqs: number of virtqueues supported by this device
> *
> - * Returns an error when fail to add to vDPA bus
> + * Return: Returns an error when fail to add to vDPA bus
> */
> int vdpa_register_device(struct vdpa_device *vdev, int nvqs)
> {
> @@ -218,7 +218,7 @@ EXPORT_SYMBOL_GPL(vdpa_unregister_device);
> * @drv: the vdpa device driver to be registered
> * @owner: module owner of the driver
> *
> - * Returns an err when fail to do the registration
> + * Return: Returns an err when fail to do the registration
> */
> int __vdpa_register_driver(struct vdpa_driver *drv, struct module *owner)
> {
> @@ -245,6 +245,8 @@ EXPORT_SYMBOL_GPL(vdpa_unregister_driver);
> * @mdev: Pointer to vdpa management device
> * vdpa_mgmtdev_register() register a vdpa management device which supports
> * vdpa device management.
> + * Return: Returns 0 on success or failure when required callback ops are not
> + * initialized.
> */
> int vdpa_mgmtdev_register(struct vdpa_mgmt_dev *mdev)
> {
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2021-04-07 3:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 17:04 [PATCH linux-next v2 00/14] vdpa: Enable user to set mac address, mtu Parav Pandit
2021-04-06 17:04 ` [PATCH linux-next v2 01/14] vdpa: Follow kdoc comment style Parav Pandit
2021-04-07 3:08 ` Jason Wang
2021-04-06 17:04 ` [PATCH linux-next v2 02/14] " Parav Pandit
2021-04-07 3:09 ` Jason Wang [this message]
2021-04-06 17:04 ` [PATCH linux-next v2 03/14] vdpa: Introduce and use vdpa device get, set config, features helpers Parav Pandit
2021-04-07 3:18 ` [PATCH linux-next v2 03/14] vdpa: Introduce and use vdpa device get,set " Jason Wang
2021-04-07 3:52 ` Parav Pandit
2021-04-06 17:04 ` [PATCH linux-next v2 04/14] vdpa: Introduce query of device config layout Parav Pandit
2021-04-07 3:56 ` Jason Wang
2021-04-07 5:10 ` Parav Pandit
2021-04-07 7:12 ` Jason Wang
2021-04-08 6:23 ` Parav Pandit
2021-04-06 17:04 ` [PATCH linux-next v2 05/14] vdpa: Enable user to set mac and mtu of vdpa device Parav Pandit
2021-04-07 3:59 ` Jason Wang
2021-04-06 17:04 ` [PATCH linux-next v2 06/14] vdpa_sim_net: Enable user to set mac address and mtu Parav Pandit
2021-04-06 17:04 ` [PATCH linux-next v2 07/14] vdpa/mlx5: Use the correct dma device when registering memory Parav Pandit
2021-04-07 4:00 ` Jason Wang
2021-04-06 17:04 ` [PATCH linux-next v2 08/14] vdpa/mlx5: Retrieve BAR address suitable any function Parav Pandit
2021-04-07 5:32 ` Jason Wang
2021-04-06 17:04 ` [PATCH linux-next v2 09/14] vdpa/mlx5: Enable user to add/delete vdpa device Parav Pandit
2021-04-06 17:04 ` [PATCH linux-next v2 10/14] vdpa/mlx5: Support configuration of MAC Parav Pandit
2021-04-07 7:21 ` Jason Wang
2021-04-06 17:04 ` [PATCH linux-next v2 11/14] vdpa/mlx5: Forward only packets with allowed MAC address Parav Pandit
2021-04-06 17:04 ` [PATCH linux-next v2 12/14] vdpa/mlx5: should exclude header length and fcs from mtu Parav Pandit
2021-04-06 17:04 ` [PATCH linux-next v2 13/14] vdpa/mlx5: Fix suspend/resume index restoration Parav Pandit
2021-04-07 7:25 ` Jason Wang
[not found] ` <20210407101612.GB207753@mtl-vdi-166.wap.labs.mlnx>
2021-04-07 13:38 ` Michael S. Tsirkin
2021-04-06 17:04 ` [PATCH linux-next v2 14/14] vdpa/mlx5: Fix wrong use of bit numbers Parav Pandit
2021-04-07 7:25 ` Jason Wang
2021-04-07 7:28 ` Parav Pandit
2021-04-07 7:28 ` [PATCH linux-next v2 00/14] vdpa: Enable user to set mac address, mtu Jason Wang
2021-04-08 3:45 ` Parav Pandit
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=ee143a65-a1ec-ae4f-4ad6-61d8797ae877@redhat.com \
--to=jasowang@redhat.com \
--cc=elic@nvidia.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=virtualization@lists.linux-foundation.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).