[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56b9dab5-6a3d-58ff-69c9-7abaabf41d05@isovalent.com>
Date: Mon, 7 Mar 2022 17:06:17 +0000
From: Quentin Monnet <quentin@...valent.com>
To: Yuntao Wang <ytcoode@...il.com>, bpf@...r.kernel.org
Cc: Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>,
Martin KaFai Lau <kafai@...com>,
Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>,
John Fastabend <john.fastabend@...il.com>,
KP Singh <kpsingh@...nel.org>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH bpf-next] bpf: Remove redundant slash
2022-03-06 00:10 UTC+0800 ~ Yuntao Wang <ytcoode@...il.com>
> The trailing slash of LIBBPF_SRCS is redundant, remove it.
>
> Signed-off-by: Yuntao Wang <ytcoode@...il.com>
> ---
> kernel/bpf/preload/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/bpf/preload/Makefile b/kernel/bpf/preload/Makefile
> index 167534e3b0b4..7b62b3e2bf6d 100644
> --- a/kernel/bpf/preload/Makefile
> +++ b/kernel/bpf/preload/Makefile
> @@ -1,6 +1,6 @@
> # SPDX-License-Identifier: GPL-2.0
>
> -LIBBPF_SRCS = $(srctree)/tools/lib/bpf/
> +LIBBPF_SRCS = $(srctree)/tools/lib/bpf
> LIBBPF_INCLUDE = $(LIBBPF_SRCS)/..
>
> obj-$(CONFIG_BPF_PRELOAD_UMD) += bpf_preload.o
Looks good to me, but we could maybe just as well get rid of LIBBPF_SRCS
in this file?:
LIBBPF_INCLUDE = $(srctree)/tools/lib
Quentin
Powered by blists - more mailing lists