From: Thomas Monjalon <thomas@monjalon.net>
To: "A.McLoughlin" <aideen.mcloughlin@intel.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
marko.kovacevic@intel.com, john.mcnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH] doc/api: add missing header file to API documentation
Date: Mon, 08 Jul 2019 21:52:37 +0200 [thread overview]
Message-ID: <4268851.pKjgac9LbL@xps> (raw)
In-Reply-To: <fd85da80-2c6a-c739-ac54-dccb3522c2eb@intel.com>
26/06/2019 18:32, Ferruh Yigit:
> On 6/26/2019 4:20 PM, A.McLoughlin wrote:
> > The APIs in the rte_bus_vdev.h file were not part of the API
> > documentation. I added this header file to the doxygen config file with
> > the name vdev.
> >
> > Signed-off-by: A.McLoughlin <aideen.mcloughlin@intel.com>
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
I suspect there are more to add to doxygen.
Applied, thanks
prev parent reply other threads:[~2019-07-08 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 15:20 A.McLoughlin
2019-06-26 16:32 ` Ferruh Yigit
2019-07-08 19:52 ` Thomas Monjalon [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=4268851.pKjgac9LbL@xps \
--to=thomas@monjalon.net \
--cc=aideen.mcloughlin@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@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).