[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEf4BzYBUVJTexS8h0smJiw09V_W+C_AeRyDbFvCum2ESzPO6g@mail.gmail.com>
Date: Mon, 30 Sep 2019 16:30:02 -0700
From: Andrii Nakryiko <andrii.nakryiko@...il.com>
To: Jakub Kicinski <jakub.kicinski@...ronome.com>
Cc: Song Liu <liu.song.a23@...il.com>,
Andrii Nakryiko <andriin@...com>, bpf <bpf@...r.kernel.org>,
Networking <netdev@...r.kernel.org>,
Alexei Starovoitov <ast@...com>,
Daniel Borkmann <daniel@...earbox.net>,
Kernel Team <kernel-team@...com>
Subject: Re: [PATCH bpf-next 2/6] libbpf: move bpf_helpers.h, bpf_endian.h
into libbpf
On Mon, Sep 30, 2019 at 4:18 PM Jakub Kicinski
<jakub.kicinski@...ronome.com> wrote:
>
> On Mon, 30 Sep 2019 15:58:35 -0700, Andrii Nakryiko wrote:
> > On Mon, Sep 30, 2019 at 3:55 PM Song Liu <liu.song.a23@...il.com> wrote:
> > >
> > > On Mon, Sep 30, 2019 at 1:43 PM Andrii Nakryiko <andriin@...com> wrote:
> > > >
> > > > Make bpf_helpers.h and bpf_endian.h official part of libbpf. Ensure they
> > > > are installed along the other libbpf headers.
> > > >
> > > > Signed-off-by: Andrii Nakryiko <andriin@...com>
> > >
> > > Can we merge/rearrange 2/6 and 3/6, so they is a git-rename instead of
> > > many +++ and ---?
> >
> > I arranged them that way because of Github sync. We don't sync
> > selftests/bpf changes to Github, and it causes more churn if commits
> > have a mix of libbpf and selftests changes.
> >
> > I didn't modify bpf_helpers.h/bpf_endian.h between those patches, so
> > don't worry about reviewing contents ;)
>
> I thought we were over this :/ Please merge the patches.
I'll merge those two patches, our sync script can handle that now,
though with a bit of human input. I'm not exactly sure on the "why"
though, I think generally splitting libbpf changes and selftests
changes is a good thing, no?
Powered by blists - more mailing lists