From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 97304A0597; Wed, 8 Apr 2020 19:41:45 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 91A611C199; Wed, 8 Apr 2020 19:41:44 +0200 (CEST) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by dpdk.org (Postfix) with ESMTP id 977CD1C12A for ; Wed, 8 Apr 2020 19:41:42 +0200 (CEST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 130605BF; Wed, 8 Apr 2020 13:41:41 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 08 Apr 2020 13:41:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=MpZzZDyQRgzgGa1E8w3HF+33Mz2kqm2XcrquXtzlXC8=; b=PIwC/f/H4zkH EFYTjzHxdksm9sbbi8Wi1mq3f2T1HW1HXCkvVTLVU8VnW7jflvm16drFlA7wgdFo DWoGjHXdYbPw3pCX5RyIeTlkMp+0Zcs+PMoqMhkeGbqTPmxUA5U/7xm4mRex5i8Q f3xTVwLFtR+2avGMX1X/7WHKjjJbDHQ= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=MpZzZDyQRgzgGa1E8w3HF+33Mz2kqm2XcrquXtzlX C8=; b=WjoX1oVEuw3TGIlE4Oy/Ymw5VkvkBRVqJdrCgHGQZrSIY/X446la0UzUZ o7pW+nC0FbGntrTGJFJuDshrYoicFsoi4ilamTy1G2w4tBWTSzP7uzNNJZMMc6/u lWSrm0b+sVp9zHgCEP+PfkLMzqor1V/aJKPiO6IchAtg4q/oi5OXgqJbqwIlLkVk eofJGJJKOsm7Dd7Vnh+dJTbnMj946SOWp+KHh4Fipk1aJHXAV3WKbe9nr3j5bK32 0L5tJJrbESsoKba6idHg0KgOTcBB2TAbBoaHrJbxq6bRcx4xzpEoPvmkER7edZaC u8q1NtnQ6PeuaxZblQ/Ej2hAtA43A== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrudejgdduudegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuff homhgrihhnpeguphgukhdrohhrghenucfkphepjeejrddufeegrddvtdefrddukeegnecu vehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrg hssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id DF706328005E; Wed, 8 Apr 2020 13:41:38 -0400 (EDT) From: Thomas Monjalon To: Neil Horman , Kevin Laatz , Ray Kinsella Cc: David Marchand , dev Date: Wed, 08 Apr 2020 19:41:36 +0200 Message-ID: <2084092.Mh6RI2rZIc@thomas> In-Reply-To: References: <20200406193430.81268-1-nhorman@tuxdriver.com> <35252260.WIbDr2VvFA@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] Remove abi_versioning.sh from tree X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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