On Thu, Jan 10, 2019 at 11:31:31AM +, Burakov, Anatoly wrote:
> On 10-Jan-19 11:11 AM, 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
On Thu, Jan 10, 2019 at 01:53:20PM +0100, David Marchand wrote:
>On Thu, Jan 10, 2019 at 1:28 PM David Marchand
><[1]david.march...@redhat.com> wrote:
>
>On Thu, Jan 10, 2019 at 12:12 PM Bruce Richardson
><[2]bruce.richard...@intel.com> wrote:
>
> Since compat library is only
On Thu, Jan 10, 2019 at 1:28 PM David Marchand
wrote:
>
>
> On Thu, Jan 10, 2019 at 12:12 PM Bruce Richardson <
> bruce.richard...@intel.com> 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 downs
On Thu, Jan 10, 2019 at 12:12 PM Bruce Richardson <
bruce.richard...@intel.com> 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 an
On 10-Jan-19 11:11 AM, 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
built before EAL depend on it
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 the case, so there
are
6 matches
Mail list logo
