From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, Maxime Coquelin <maxime.coquelin@redhat.com>,
Tiwei Bie <tiwei.bie@intel.com>,
Zhihong Wang <zhihong.wang@intel.com>,
xiao.w.wang@intel.com
Subject: Re: [dpdk-dev] [PATCH] vhost: add doxygen comment to vDPA header
Date: Fri, 12 Oct 2018 04:25:08 +0800 [thread overview]
Message-ID: <20181011202508.GA85553@intel.com> (raw)
In-Reply-To: <d398e396-8bc0-9a08-f5ed-9321a3cc7d57@intel.com>
On 10/11, Ferruh Yigit wrote:
>On 10/10/2018 10:14 AM, Xiaolong Ye wrote:
>> As APIs in rte_vdpa.h are public, we need to add doxygen comments
>> to all APIs and structures.
>>
>> Signed-off-by: Xiaolong Ye <xiaolong.ye@intel.com>
>
><...>
>
>> @@ -29,6 +32,9 @@ struct rte_vdpa_dev_addr {
>> };
>> };
>>
>> +/**
>> + * vdpa device operations
>> + */
>> struct rte_vdpa_dev_ops {
>> /* Get capabilities of this device */
>> int (*get_queue_num)(int did, uint32_t *queue_num);
>
>Can you please document all fields of the structs?
>This is part of public API and needs to be documented properly, if possible more
>detail on struct documentation will be good.
>
Got it, I'll add more descriptions.
><...>
>
>> -/* Register a vdpa device, return did if successful, -1 on failure */
>> +/**
>> + * Register a vdpa device
>> + *
>> + * @param addr
>> + * the vdpa device address
>> + * @parm ops
>> + * the vdpa device operations
>> + * @return
>> + * device id on success, -1 on failure
>> + */
>> int __rte_experimental
>> rte_vdpa_register_device(struct rte_vdpa_dev_addr *addr,
>> struct rte_vdpa_dev_ops *ops);
>
>For experimental APIs we tend to add following into function comment:
> * @warning
> * @b EXPERIMENTAL: this API may change without prior notice
>
>Please check lib/librte_member/rte_member.h for samples.
Got it.
Thanks,
Xiaolong
prev parent reply other threads:[~2018-10-11 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 9:14 Xiaolong Ye
2018-10-11 12:42 ` Maxime Coquelin
2018-10-11 13:28 ` Ferruh Yigit
2018-10-11 20:25 ` Ye Xiaolong [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=20181011202508.GA85553@intel.com \
--to=xiaolong.ye@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=tiwei.bie@intel.com \
--cc=xiao.w.wang@intel.com \
--cc=zhihong.wang@intel.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).