From: David Marchand <david.marchand@redhat.com>
To: dev <dev@dpdk.org>
Cc: Neil Horman <nhorman@tuxdriver.com>,
Thomas Monjalon <thomas@monjalon.net>,
Amr Mokhtar <amr.mokhtar@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
declan.doherty@intel.com,
Maxime Coquelin <maxime.coquelin@redhat.com>,
tiwei.bie@intel.com, zhihong.wang@intel.com
Subject: Re: [dpdk-dev] [RFC PATCH] detect missing experimental tags in headers
Date: Mon, 1 Apr 2019 09:10:06 +0200 [thread overview]
Message-ID: <CAJFAV8zoe3c1LUxfo=SLZGw3HTn4w3BhbiX5QGJr_6pry1+4Tg@mail.gmail.com> (raw)
In-Reply-To: <1545227093-25493-1-git-send-email-david.marchand@redhat.com>
On Wed, Dec 19, 2018 at 2:45 PM David Marchand <david.marchand@redhat.com>
wrote:
> Add a little script to get the symbols of a given section looking at a
> library map file, then, on installation, inspect the sources headers to
> check that the declaration of the EXPERIMENTAL symbols are prefixed with
> a __rte_experimental tag.
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
>
> For now, the check is not fatal, since this is just a draft.
> Finding out the right headers could be improved.
> We could also move this check to checkpatches so that it is enforced by
> maintainers.
>
Never got any review/comment, if you try with current origin/master, there
is a little update to do for the eal directory hack:
- if [ "$${srcdir%%linuxapp/eal}" != "$$srcdir" ]; then \
- srcdir="$$srcdir $${srcdir%%linuxapp/eal}common"; \
+ if [ "$${srcdir%%/eal}" != "$$srcdir" ]; then \
+ srcdir="$$srcdir $${srcdir%/*/eal}/common"; \
I did not catch false positive so far.
Surely there could be problems with the grep regexp, but if we have this in
the build framework, people will get errors before submitting.
Btw, I caught some warnings in the following components.
CC relevant maintainers, can you look at this ?
== Build lib/librte_bbdev
ERROR: rte_bbdev_devices is not marked as experimental in this library
headers
This symbol is in the map file but is neither marked in header nor in the
code.
This is an array, does it qualify as an experimental API?
== Build lib/librte_cryptodev
ERROR: rte_crypto_asym_op_strings is not marked as experimental in this
library headers
ERROR: rte_crypto_asym_xform_strings is not marked as experimental in this
library headers
Idem.
== Build lib/librte_vhost
ERROR: rte_vhost_va_from_guest_pa is not marked as experimental in this
library headers
This symbol is in the map file but is neither marked in header nor in the
code.
Here, this is an inline, not sure the experimental tag is that useful
(except documenting it is experimental?).
--
David Marchand
next prev parent reply other threads:[~2019-04-01 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 13:44 David Marchand
2019-04-01 7:10 ` David Marchand [this message]
2019-04-01 7:10 ` David Marchand
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='CAJFAV8zoe3c1LUxfo=SLZGw3HTn4w3BhbiX5QGJr_6pry1+4Tg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=amr.mokhtar@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=nhorman@tuxdriver.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=thomas@monjalon.net \
--cc=tiwei.bie@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).