DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hurd <stephen.hurd@broadcom.com>,
	Ajit Khaparde <ajit.khaparde@broadcom.com>
Cc: John McNamara <john.mcnamara@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 2/2] doc: add API documentation for bnxt PMD
Date: Mon, 11 Sep 2017 17:36:21 +0100	[thread overview]
Message-ID: <ff96a0d0-40f7-4432-6af2-94ff7546dc4b@intel.com> (raw)
In-Reply-To: <20170911163335.50221-2-ferruh.yigit@intel.com>

On 9/11/2017 5:33 PM, Ferruh Yigit wrote:
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
>  doc/api/doxy-api-index.md | 1 +
>  doc/api/doxy-api.conf     | 1 +
>  2 files changed, 2 insertions(+)
> 
> diff --git a/doc/api/doxy-api-index.md b/doc/api/doxy-api-index.md
> index 19e0d4f3d..1e8068d7c 100644
> --- a/doc/api/doxy-api-index.md
> +++ b/doc/api/doxy-api-index.md
> @@ -55,6 +55,7 @@ The public API headers are grouped by topics:
>    [KNI]                (@ref rte_kni.h),
>    [ixgbe]              (@ref rte_pmd_ixgbe.h),
>    [i40e]               (@ref rte_pmd_i40e.h),
> +  [bnxt]               (@ref rte_pmd_bnxt.h),

Hi Stephen, Ajit,

Can you please update header file with doxygen comments? Since it is
public header file now, APIs should be documented properly.

Thanks,
ferruh

>    [crypto_scheduler]   (@ref rte_cryptodev_scheduler.h)

<...>

  reply	other threads:[~2017-09-11 16:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-11 16:33 [dpdk-dev] [PATCH 1/2] doc: add shared library versions for missing PMDs Ferruh Yigit
2017-09-11 16:33 ` [dpdk-dev] [PATCH 2/2] doc: add API documentation for bnxt PMD Ferruh Yigit
2017-09-11 16:36   ` Ferruh Yigit [this message]
2017-09-18 18:22   ` Mcnamara, John
2017-09-18 18:22 ` [dpdk-dev] [PATCH 1/2] doc: add shared library versions for missing PMDs Mcnamara, John
2017-10-06 21:00   ` Ferruh Yigit
2017-09-27 18:58 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2017-09-28  2:04   ` Yang, Zhiyong
2017-10-04 21:38     ` Thomas Monjalon

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=ff96a0d0-40f7-4432-6af2-94ff7546dc4b@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=stephen.hurd@broadcom.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).