Re: [dpdk-dev] [PATCH v3] compat: merge compat library into EAL

2019-02-25 Thread Thomas Monjalon
06/02/2019 12:01, Bruce Richardson: > Since compat library is only a single header, we can easily move it into > the EAL common headers instead of tracking it separately. The downside of > this is that it becomes a little more difficult to have any libs that are > built before EAL depend on it. Tha

Re: [dpdk-dev] [PATCH v3] compat: merge compat library into EAL

2019-02-25 Thread Bruce Richardson
On Fri, Feb 08, 2019 at 05:13:21PM +, Bruce Richardson wrote: > On Fri, Feb 08, 2019 at 11:55:09AM -0500, Neil Horman wrote: > > On Fri, Feb 08, 2019 at 04:18:38PM +, Bruce Richardson wrote: > > > On Fri, Feb 08, 2019 at 10:37:40AM -0500, Neil Horman wrote: > > > > On Thu, Feb 07, 2019 at 0

Re: [dpdk-dev] [PATCH v3] compat: merge compat library into EAL

2019-02-08 Thread Bruce Richardson
On Fri, Feb 08, 2019 at 11:55:09AM -0500, Neil Horman wrote: > On Fri, Feb 08, 2019 at 04:18:38PM +, Bruce Richardson wrote: > > On Fri, Feb 08, 2019 at 10:37:40AM -0500, Neil Horman wrote: > > > On Thu, Feb 07, 2019 at 03:03:28PM +, Bruce Richardson wrote: > > > > On Thu, Feb 07, 2019 at 0

Re: [dpdk-dev] [PATCH v3] compat: merge compat library into EAL

2019-02-08 Thread Neil Horman
On Fri, Feb 08, 2019 at 04:18:38PM +, Bruce Richardson wrote: > On Fri, Feb 08, 2019 at 10:37:40AM -0500, Neil Horman wrote: > > On Thu, Feb 07, 2019 at 03:03:28PM +, Bruce Richardson wrote: > > > On Thu, Feb 07, 2019 at 09:34:26AM -0500, Neil Horman wrote: > > > > On Wed, Feb 06, 2019 at 0

Re: [dpdk-dev] [PATCH v3] compat: merge compat library into EAL

2019-02-08 Thread Bruce Richardson
On Fri, Feb 08, 2019 at 10:37:40AM -0500, Neil Horman wrote: > On Thu, Feb 07, 2019 at 03:03:28PM +, Bruce Richardson wrote: > > On Thu, Feb 07, 2019 at 09:34:26AM -0500, Neil Horman wrote: > > > On Wed, Feb 06, 2019 at 02:17:45PM +, Bruce Richardson wrote: > > > > On Wed, Feb 06, 2019 at 0

Re: [dpdk-dev] [PATCH v3] compat: merge compat library into EAL

2019-02-08 Thread Neil Horman
On Thu, Feb 07, 2019 at 03:03:28PM +, Bruce Richardson wrote: > On Thu, Feb 07, 2019 at 09:34:26AM -0500, Neil Horman wrote: > > On Wed, Feb 06, 2019 at 02:17:45PM +, Bruce Richardson wrote: > > > On Wed, Feb 06, 2019 at 07:22:54AM -0500, Neil Horman wrote: > > > > On Wed, Feb 06, 2019 at 1

Re: [dpdk-dev] [PATCH v3] compat: merge compat library into EAL

2019-02-07 Thread Bruce Richardson
On Thu, Feb 07, 2019 at 09:34:26AM -0500, Neil Horman wrote: > On Wed, Feb 06, 2019 at 02:17:45PM +, Bruce Richardson wrote: > > On Wed, Feb 06, 2019 at 07:22:54AM -0500, Neil Horman wrote: > > > On Wed, Feb 06, 2019 at 11:01:30AM +, Bruce Richardson wrote: > > > > Since compat library is o

Re: [dpdk-dev] [PATCH v3] compat: merge compat library into EAL

2019-02-07 Thread Neil Horman
On Wed, Feb 06, 2019 at 02:17:45PM +, Bruce Richardson wrote: > On Wed, Feb 06, 2019 at 07:22:54AM -0500, Neil Horman wrote: > > On Wed, Feb 06, 2019 at 11:01:30AM +, Bruce Richardson wrote: > > > Since compat library is only a single header, we can easily move it into > > > the EAL common

Re: [dpdk-dev] [PATCH v3] compat: merge compat library into EAL

2019-02-06 Thread Bruce Richardson
On Wed, Feb 06, 2019 at 07:22:54AM -0500, Neil Horman wrote: > On Wed, Feb 06, 2019 at 11:01:30AM +, Bruce Richardson wrote: > > Since compat library is only a single header, we can easily move it into > > the EAL common headers instead of tracking it separately. The downside of > > this is tha

Re: [dpdk-dev] [PATCH v3] compat: merge compat library into EAL

2019-02-06 Thread Neil Horman
On Wed, Feb 06, 2019 at 11:01:30AM +, Bruce Richardson wrote: > Since compat library is only a single header, we can easily move it into > the EAL common headers instead of tracking it separately. The downside of > this is that it becomes a little more difficult to have any libs that are > buil

[dpdk-dev] [PATCH v3] compat: merge compat library into EAL

2019-02-06 Thread Bruce Richardson
Since compat library is only a single header, we can easily move it into the EAL common headers instead of tracking it separately. The downside of this is that it becomes a little more difficult to have any libs that are built before EAL depend on it. Thankfully, this is not a major problem as the