From: David Marchand <david.marchand@redhat.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: thomas@monjalon.net, "Yigit, Ferruh" <ferruh.yigit@intel.com>,
dev@dpdk.org, Timothy Redaelli <tredaelli@redhat.com>,
adrien.mazarguil@6wind.com
Subject: Re: [dpdk-dev] Marking symbols as experimental in the headers only
Date: Tue, 18 Dec 2018 13:27:29 +0100 [thread overview]
Message-ID: <CAJFAV8zTkFUYofqKor_mXt6nvg8SPdFn+fPhx6MYkN=TNHaSkQ@mail.gmail.com> (raw)
In-Reply-To: <20181218122500.GB2078@hmswarspite.think-freely.org>
On Tue, Dec 18, 2018 at 1:25 PM Neil Horman <nhorman@tuxdriver.com> wrote:
> On Tue, Dec 18, 2018 at 11:41:34AM +0100, David Marchand wrote:
>
> > The real issue in the end is that the __rte_experimental in headers is
> the
> > most important thing and can be missed during reviews.
> > But I found no easy way to detect this.
> >
> > Do you have any idea ?
> >
> The most direct way is to add a regular expression search to the script
> that
> checks the object files. That would be some tricky grep/awk magic, but it
> should be possible
>
This is what I feared :-).
Ok, I will have a try.
--
David Marchand
next prev parent reply other threads:[~2018-12-18 12:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 13:01 David Marchand
2018-12-03 13:26 ` Ferruh Yigit
2018-12-03 16:47 ` Neil Horman
2018-12-04 8:21 ` David Marchand
2018-12-04 15:14 ` Neil Horman
2018-12-04 20:48 ` David Marchand
2018-12-04 21:34 ` Richardson, Bruce
2018-12-05 12:21 ` Neil Horman
2018-12-05 13:22 ` David Marchand
2018-12-18 10:41 ` David Marchand
2018-12-18 12:25 ` Neil Horman
2018-12-18 12:27 ` David Marchand [this message]
2018-12-19 9:12 ` David Marchand
2018-12-19 12:39 ` Neil Horman
2018-12-19 13:46 ` 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='CAJFAV8zTkFUYofqKor_mXt6nvg8SPdFn+fPhx6MYkN=TNHaSkQ@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=nhorman@tuxdriver.com \
--cc=thomas@monjalon.net \
--cc=tredaelli@redhat.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).