Re: [dpdk-dev] [PATCH 0/5] dpdk: enhance EXPERIMENTAL api tagging

2018-01-31 Thread Thomas Monjalon
31/01/2018 13:18, Neil Horman: > On Tue, Jan 30, 2018 at 05:15:01PM +0100, Thomas Monjalon wrote: > > 30/01/2018 16:54, Neil Horman: > > > On Mon, Jan 29, 2018 at 10:46:27PM +0100, Thomas Monjalon wrote: > > > > 22/01/2018 02:48, Neil Horman: > > > > > v5 Changes > > > > > * Clean ups suggested by

Re: [dpdk-dev] [PATCH 0/5] dpdk: enhance EXPERIMENTAL api tagging

2018-01-31 Thread Neil Horman
On Tue, Jan 30, 2018 at 05:15:01PM +0100, Thomas Monjalon wrote: > 30/01/2018 16:54, Neil Horman: > > On Mon, Jan 29, 2018 at 10:46:27PM +0100, Thomas Monjalon wrote: > > > 22/01/2018 02:48, Neil Horman: > > > > v5 Changes > > > > * Clean ups suggested by Thomas > > > > > > There were a lot of new

Re: [dpdk-dev] [PATCH 0/5] dpdk: enhance EXPERIMENTAL api tagging

2018-01-30 Thread Thomas Monjalon
30/01/2018 16:54, Neil Horman: > On Mon, Jan 29, 2018 at 10:46:27PM +0100, Thomas Monjalon wrote: > > 22/01/2018 02:48, Neil Horman: > > > v5 Changes > > > * Clean ups suggested by Thomas > > > > There were a lot of new functions to tag when rebasing this v5. > > Rebased and applied, thanks. > >

Re: [dpdk-dev] [PATCH 0/5] dpdk: enhance EXPERIMENTAL api tagging

2018-01-30 Thread Neil Horman
On Mon, Jan 29, 2018 at 10:46:27PM +0100, Thomas Monjalon wrote: > 22/01/2018 02:48, Neil Horman: > > v5 Changes > > * Clean ups suggested by Thomas > > There were a lot of new functions to tag when rebasing this v5. > Rebased and applied, thanks. > Sorry, not clear what you mean by this. Are y

Re: [dpdk-dev] [PATCH 0/5] dpdk: enhance EXPERIMENTAL api tagging

2018-01-29 Thread Thomas Monjalon
22/01/2018 02:48, Neil Horman: > v5 Changes > * Clean ups suggested by Thomas There were a lot of new functions to tag when rebasing this v5. Rebased and applied, thanks.

[dpdk-dev] [PATCH 0/5] dpdk: enhance EXPERIMENTAL api tagging

2018-01-21 Thread Neil Horman
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 follow