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

08/04/2020 16:34, Ray Kinsella:
> On 07/04/2020 12:58, Thomas Monjalon wrote:
> > 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?

Sorry I was probably not clear.
I am talking about all ABI discussions we have in general
on the mailing list.
Sometimes we need help with the tools, sometimes with the doc,
more often we need helping those having ABI issues or questions.
If we don't timely reply to all concerns, ABI enforcement fails.

And let's be even clearer:
I feel too many ABI concerns are managed by David and myself.


> > 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. 

Please help in emails about ABI issues, including rte_internal marker:
	http://inbox.dpdk.org/dev/?q=ABI
Thanks



  reply	other threads:[~2020-04-08 17:41 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
2020-04-08 17:41         ` Thomas Monjalon [this message]
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=2084092.Mh6RI2rZIc@thomas \
    --to=thomas@monjalon.net \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=kevin.laatz@intel.com \
    --cc=mdr@ashroe.eu \
    --cc=nhorman@tuxdriver.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).