On Fri, May 3, 2019 at 2:09 PM Y Song wrote:
>
> On Fri, May 3, 2019 at 12:54 PM William Tu wrote:
> >
> > On Thu, May 2, 2019 at 1:18 PM Y Song wrote:
> > >
> > > On Thu, May 2, 2019 at 11:34 AM William Tu wrote:
> > > >
> > > > The libbpf_util.h is used by xsk.h, so add it to
> > > > the inst
On Fri, May 3, 2019 at 12:54 PM William Tu wrote:
>
> On Thu, May 2, 2019 at 1:18 PM Y Song wrote:
> >
> > On Thu, May 2, 2019 at 11:34 AM William Tu wrote:
> > >
> > > The libbpf_util.h is used by xsk.h, so add it to
> > > the install headers.
> >
> > Can we try to change code a little bit to a
On Thu, May 2, 2019 at 1:18 PM Y Song wrote:
>
> On Thu, May 2, 2019 at 11:34 AM William Tu wrote:
> >
> > The libbpf_util.h is used by xsk.h, so add it to
> > the install headers.
>
> Can we try to change code a little bit to avoid exposing libbpf_util.h?
> Originally libbpf_util.h is considered
On Thu, May 2, 2019 at 11:34 AM William Tu wrote:
>
> The libbpf_util.h is used by xsk.h, so add it to
> the install headers.
Can we try to change code a little bit to avoid exposing libbpf_util.h?
Originally libbpf_util.h is considered as libbpf internal.
I am not strongly against this patch. Bu
