From: David Marchand <david.marchand@redhat.com>
To: Neil Horman <nhorman@tuxdriver.com>, thomas@monjalon.net
Cc: "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 11:41:34 +0100 [thread overview]
Message-ID: <CAJFAV8zy-8WT7qu+4yD1kdqX3ULoKRxM3QAW-=UAFmVj25Yxrg@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8w0zrCo+v2PHLZqhbkRMaVK5MczovtfyO2cynk6rMckBw@mail.gmail.com>
On Wed, Dec 5, 2018 at 2:22 PM David Marchand <david.marchand@redhat.com>
wrote:
>
> On Wed, Dec 5, 2018 at 1:23 PM Neil Horman <nhorman@tuxdriver.com> wrote:
>
>> On Tue, Dec 04, 2018 at 09:48:22PM +0100, David Marchand wrote:
>> > On Tue, Dec 4, 2018 at 4:16 PM Neil Horman <nhorman@tuxdriver.com>
>> wrote:
>> > > If you would like to make this adjustment, I'm fine with it, though be
>> > > aware,
>> > > you will likely need to make some adjustments to the
>> > > check-experimental-syms
>> > > script to account for this
>> > >
>> >
>> > I am not sure I see what you mean on check-experimental-syms.sh.
>> > I would only do a s/definition/declaration/ in the error message.
>> > Do you have something else in mind ?
>> All I was saying was that if you wanted to document the policy change,
>> you might
>> need to check that script as its a reflection of that policy, and I
>> couldn't
>> recall if it was grepping through .c and .h files (which might imply it
>> needs to
>> change to reflect this policy). I just looked however, and its checking
>> object
>> files, so you should be ok.
>>
>
> Yes, thanks for the confirmation.
>
I have given it some more thought and did not send my patch that removes
all __rte_experimental from the definitions sites.
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 ?
--
David Marchand
next prev parent reply other threads:[~2018-12-18 10:41 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 [this message]
2018-12-18 12:25 ` Neil Horman
2018-12-18 12:27 ` David Marchand
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='CAJFAV8zy-8WT7qu+4yD1kdqX3ULoKRxM3QAW-=UAFmVj25Yxrg@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).