From: Akhil Goyal <akhil.goyal@nxp.com>
To: Anoob Joseph <anoobj@marvell.com>,
Radu Nicolau <radu.nicolau@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Thomas Monjalon <thomas@monjalon.net>
Cc: "konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
"bernard.iremonger@intel.com" <bernard.iremonger@intel.com>,
"declan.doherty@intel.com" <declan.doherty@intel.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] [EXT] [PATCH] security: update doxygen fields
Date: Wed, 4 Sep 2019 09:27:26 +0000 [thread overview]
Message-ID: <VE1PR04MB66396B770F9C546EC1E1D086E6B80@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <MN2PR18MB287767C0B84670901EBBD1B9DFB80@MN2PR18MB2877.namprd18.prod.outlook.com>
>
> Hi Radu,
>
> Most parts of the file(rte_security.h) follows 'description after item'
> methodology. Do you think we should stick to that?
>
> @Akhil, @Thomas, what is the recommended way of documenting individual
> members of structure? Is it 'description after the item' or 'description before the
> item'?
>
Recommended way is as suggested by Thomas(in other email) and that can be done separately.
However it is not a documentation bug but this patch resolves a bug in the documentation
which should be backported as well.
-Akhil
next prev parent reply other threads:[~2019-09-04 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 12:57 [dpdk-dev] " Radu Nicolau
2019-09-04 3:41 ` [dpdk-dev] [EXT] " Anoob Joseph
2019-09-04 7:46 ` Thomas Monjalon
2019-09-04 9:27 ` Akhil Goyal [this message]
2019-09-04 9:18 ` [dpdk-dev] " Akhil Goyal
2019-09-04 9:27 ` [dpdk-dev] [EXT] " Anoob Joseph
2019-09-04 11:03 ` [dpdk-dev] [PATCH v2] " Radu Nicolau
2019-09-19 15:10 ` Akhil Goyal
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=VE1PR04MB66396B770F9C546EC1E1D086E6B80@VE1PR04MB6639.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=bernard.iremonger@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=radu.nicolau@intel.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).