DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ray Kinsella <mdr@ashroe.eu>
To: Thomas Monjalon <thomas@monjalon.net>,
	David Marchand <david.marchand@redhat.com>,
	Neil Horman <nhorman@tuxdriver.com>,
	Kevin Laatz <kevin.laatz@intel.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] Remove abi_versioning.sh from tree
Date: Wed, 8 Apr 2020 15:34:35 +0100	[thread overview]
Message-ID: <c0cd793b-5f2c-1b4b-dc0b-3be0eec539fd@ashroe.eu> (raw)
In-Reply-To: <35252260.WIbDr2VvFA@thomas>



On 07/04/2020 12:58, Thomas Monjalon wrote:
> 07/04/2020 13:33, Neil Horman:
>> On Tue, Apr 07, 2020 at 09:36:17AM +0200, David Marchand wrote:
>>> On Mon, Apr 6, 2020 at 9:34 PM Neil Horman <nhorman@tuxdriver.com> wrote:
>>>>
>>>> Since we've moved away from our initial abi_versioning.sh script, in
>>>
>>> abi_versioning.sh does not exist (idem with the patch title).
>>> I suppose you meant validate-abi.sh.
>>>
>> Crud, you're right, I was convoluting terms, sorry.  Shall I repost with a
>> corrected changelog?
> 
> Not only the commit log, look below how you did not care about the basic
> usage of the new tool.
> 
> 
>>>> favor of check_abi.sh, which uses libabigail, remove the old script from
>>>
>>> check-abi.sh
>>>
>>>> the tree, and update the docs accordingly
> [...]
>>>> --- a/doc/guides/contributing/abi_versioning.rst
>>>> +++ b/doc/guides/contributing/abi_versioning.rst
> 
> The maintainer of doc/guides/contributing/abi_*.rst
> is Ray Kinsella so I add him as Cc.

Thanks for that ... 

> 
> [...]
>>>> -The syntax of the ``validate-abi.sh`` utility is::
>>>> +The syntax of the ``check-abi.sh`` utility is::
>>>>
>>>> -   ./devtools/validate-abi.sh <REV1> <REV2>
>>>> +   ./devtools/check-abi.sh <REV1> <REV2>
>>>
>>> The new script is not a direct replacement.
>>> It won't take git revisions, but build directories where versions of
>>> dpdk have been compiled.
>>>
>>> devtools/test-build.sh and devtools/test-meson-builds.sh illustrate its use.
>>> https://git.dpdk.org/dpdk/tree/devtools/test-meson-builds.sh#n127
> 
> David, I think Neil did not take time to understand what changed in
> ABI tooling.
> I really wonder who is the real maintainer of ABI tooling and policy.
> Neil, Ray, I was expecting a better involvement in this major
> policy enforcement.

I missed it on the ML, was check-maintainers.sh run?
I am just getting FYI'ed now, right?

> 
> This is where we are:
> 	- Neil asked first for ABI compatibility
> 	- Neil created validate-abi.sh
> 	- Ray asked for a strict policy

Feedback on that separately. 

> 	- Kevin worked on a new tooling
> 	- David completed the tooling work
> 	- David integrated ABI checks in Travis
> 
> There are many people partly involved.
> I think we need one person truly involved in ABI questions,
> someone who feels responsible and will take care of details
> like the documentation update requested above.
> 
> Please don't rely on David and myself, we are already very busy
> with making sure every patches are properly reviewed.
> We need good help on the ABI topic in general.

Always happy to help. 



 

  parent reply	other threads:[~2020-04-08 14:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06 19:34 Neil Horman
2020-04-07  7:36 ` David Marchand
2020-04-07 11:33   ` Neil Horman
2020-04-07 11:40     ` David Marchand
2020-04-07 11:58     ` Thomas Monjalon
2020-04-07 19:52       ` Neil Horman
2020-04-08 14:34       ` Ray Kinsella [this message]
2020-04-08 17:41         ` Thomas Monjalon
2020-04-08 14:50   ` Ray Kinsella
2020-04-08 14:49 ` Ray Kinsella
2020-04-09  9:26   ` Bruce Richardson
2020-04-09 10:04     ` Ray Kinsella

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=c0cd793b-5f2c-1b4b-dc0b-3be0eec539fd@ashroe.eu \
    --to=mdr@ashroe.eu \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=kevin.laatz@intel.com \
    --cc=nhorman@tuxdriver.com \
    --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).