From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Mcnamara, John" Subject: Re: [PATCHv3 0/4] dpdk: enhance EXPERIMENTAL api tagging Date: Tue, 12 Dec 2017 14:33:13 +0000 Message-ID: References: <20171201185628.16261-1-nhorman@tuxdriver.com> <20171211193619.21643-1-nhorman@tuxdriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: "thomas@monjalon.net" , "Richardson, Bruce" To: Neil Horman , "dev@dpdk.org" Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 17F91E5D for ; Tue, 12 Dec 2017 15:33:16 +0100 (CET) In-Reply-To: <20171211193619.21643-1-nhorman@tuxdriver.com> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" > -----Original Message----- > From: Neil Horman [mailto:nhorman@tuxdriver.com] > Sent: Monday, December 11, 2017 7:36 PM > To: dev@dpdk.org > Cc: thomas@monjalon.net; Mcnamara, John ; > Richardson, Bruce > Subject: [PATCHv3 0/4] dpdk: enhance EXPERIMENTAL api tagging >=20 > Hey all- > A few days ago, I was lamenting the fact that, when reviewing > patches I would frequently complain about ABI changes that were actually > considered safe because they were part of the EXPERIMENTAL api set. John > M. asked me then what I might do to improve the situation, and the > following patch set is a proposal that I've come up with. Hi Neil, Thanks for this and apologies in advance for making more work for you but it would be good to have a short section in the Contributors Guide on how to add/check experimental APIs. I think the information in this cover letter could be repurposed along with a few code and shell examples. Probably as a new high level section in the Contributors Guides: http://dpdk.org/doc/guides/contributing/index.html Thanks, John