From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: Shahaf Shuler <shahafs@mellanox.com>,
Jan Viktorin <viktorin@rehivetech.com>,
Gavin Hu <gavin.hu@arm.com>,
Chao Zhu <chaozhu@linux.vnet.ibm.com>
Subject: Re: [dpdk-dev] [PATCH] eal: remove redundant API description
Date: Thu, 28 Mar 2019 23:53:43 +0100 [thread overview]
Message-ID: <4937558.DrODiE4unh@xps> (raw)
In-Reply-To: <AM0PR0502MB37953A97DCBB2E349111BBAEC3410@AM0PR0502MB3795.eurprd05.prod.outlook.com>
20/03/2019 07:46, Shahaf Shuler:
> Tuesday, March 19, 2019 11:16 PM, Thomas Monjalon:
> > Subject: [dpdk-dev] [PATCH] eal: remove redundant API description
> >
> > Atomic functions are described in doxygen of the file
> > lib/librte_eal/common/include/generic/rte_atomic.h
> > The copies in arch-specific files are redundant and confuse readers about the
> > genericity of the API.
> >
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
>
> Acked-by: Shahaf Shuler <shahafs@mellanox.com>
Applied
next prev parent reply other threads:[~2019-03-28 22:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 21:16 Thomas Monjalon
2019-03-19 21:16 ` Thomas Monjalon
2019-03-20 6:46 ` Shahaf Shuler
2019-03-20 6:46 ` Shahaf Shuler
2019-03-28 22:53 ` Thomas Monjalon [this message]
2019-03-28 22:53 ` 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=4937558.DrODiE4unh@xps \
--to=thomas@monjalon.net \
--cc=chaozhu@linux.vnet.ibm.com \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.com \
--cc=shahafs@mellanox.com \
--cc=viktorin@rehivetech.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).