[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YCJWTCdAjoc+N70A@krava>
Date: Tue, 9 Feb 2021 10:30:52 +0100
From: Jiri Olsa <jolsa@...hat.com>
To: Andrii Nakryiko <andrii.nakryiko@...il.com>
Cc: Jiri Olsa <jolsa@...nel.org>, Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andriin@...com>,
Networking <netdev@...r.kernel.org>, bpf <bpf@...r.kernel.org>,
Martin KaFai Lau <kafai@...com>,
Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>,
John Fastabend <john.fastabend@...il.com>,
KP Singh <kpsingh@...omium.org>,
Masahiro Yamada <masahiroy@...nel.org>,
Michal Marek <michal.lkml@...kovi.net>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>
Subject: Re: [PATCHv2 bpf-next 0/4] kbuild/resolve_btfids: Invoke
resolve_btfids clean in root Makefile
On Mon, Feb 08, 2021 at 09:36:40PM -0800, Andrii Nakryiko wrote:
> On Fri, Feb 5, 2021 at 4:45 AM Jiri Olsa <jolsa@...nel.org> wrote:
> >
> > hi,
> > resolve_btfids tool is used during the kernel build,
> > so we should clean it on kernel's make clean.
> >
> > v2 changes:
> > - add Song's acks on patches 1 and 4 (others changed) [Song]
> > - add missing / [Andrii]
> > - change srctree variable initialization [Andrii]
> > - shifted ifdef for clean target [Andrii]
> >
> > thanks,
> > jirka
> >
> >
> > ---
> > Jiri Olsa (4):
> > tools/resolve_btfids: Build libbpf and libsubcmd in separate directories
> > tools/resolve_btfids: Check objects before removing
> > tools/resolve_btfids: Set srctree variable unconditionally
> > kbuild: Add resolve_btfids clean to root clean target
> >
> > Makefile | 7 ++++++-
> > tools/bpf/resolve_btfids/.gitignore | 2 --
> > tools/bpf/resolve_btfids/Makefile | 44 ++++++++++++++++++++++----------------------
> > 3 files changed, 28 insertions(+), 25 deletions(-)
> >
>
> I've applied the changes to the bpf-next tree. Thanks.
>
> Next time please make sure that each patch in the series has a v2 tag
> in [PATCH] section, it was a bit confusing to figure out which one is
> the actual v2 version. Our tooling (CI) also expects the format [PATCH
> v2 bpf-next], so try not to merge v2 with PATCH.
>
will do, thanks
jirka
Powered by blists - more mailing lists