From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Daniel Díaz" <daniel.diaz@linaro.org>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org, mingo@redhat.com
Subject: Re: [PATCH] tools lib bpf: Fix double file test in Makefile
Date: Wed, 16 Aug 2017 23:19:30 -0300 [thread overview]
Message-ID: <20170817021930.GA6223@kernel.org> (raw)
In-Reply-To: <1502814810-960-1-git-send-email-daniel.diaz@linaro.org>
Em Tue, Aug 15, 2017 at 11:33:30AM -0500, Daniel Díaz escreveu:
> The Makefile verifies the same file exists twice:
> test -f ../../../include/uapi/linux/bpf.h -a \
> -f ../../../include/uapi/linux/bpf.h
>
> The purpose of the check is to ensure the diff (immediately
> after the test) doesn't fail with these two files:
> /tools/include/uapi/linux/bpf.h
> /include/uapi/linux/bpf.h
>
> Same recipe for bpf_common:
> test -f ../../../include/uapi/linux/bpf_common.h -a \
> -f ../../../include/uapi/linux/bpf_common.h
>
> This corrects the location of the tests.
Patch doesn't apply, conflicts with:
[acme@jouet linux]$ git log --oneline -1 8255e1efc193f
8255e1efc193 perf build: Clarify open-coded header version warning message
That is in my tip/perf/core and on tip/perf/core, that is where perf
development for next version takes place.
I'll fix it up.
Thanks,
- Arnaldo
> Signed-off-by: Daniel Díaz <daniel.diaz@linaro.org>
> ---
> tools/lib/bpf/Makefile | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/lib/bpf/Makefile b/tools/lib/bpf/Makefile
> index 1f5300e..9216c31 100644
> --- a/tools/lib/bpf/Makefile
> +++ b/tools/lib/bpf/Makefile
> @@ -154,10 +154,10 @@ all: fixdep $(VERSION_FILES) all_cmd
> all_cmd: $(CMD_TARGETS)
>
> $(BPF_IN): force elfdep bpfdep
> - @(test -f ../../../include/uapi/linux/bpf.h -a -f ../../../include/uapi/linux/bpf.h && ( \
> + @(test -f ../../include/uapi/linux/bpf.h -a -f ../../../include/uapi/linux/bpf.h && ( \
> (diff -B ../../include/uapi/linux/bpf.h ../../../include/uapi/linux/bpf.h >/dev/null) || \
> echo "Warning: tools/include/uapi/linux/bpf.h differs from kernel" >&2 )) || true
> - @(test -f ../../../include/uapi/linux/bpf_common.h -a -f ../../../include/uapi/linux/bpf_common.h && ( \
> + @(test -f ../../include/uapi/linux/bpf_common.h -a -f ../../../include/uapi/linux/bpf_common.h && ( \
> (diff -B ../../include/uapi/linux/bpf_common.h ../../../include/uapi/linux/bpf_common.h >/dev/null) || \
> echo "Warning: tools/include/uapi/linux/bpf_common.h differs from kernel" >&2 )) || true
> $(Q)$(MAKE) $(build)=libbpf
> --
> 2.7.4
prev parent reply other threads:[~2017-08-17 2:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 16:33 [PATCH] tools lib bpf: Fix double file test in Makefile Daniel Díaz
2017-08-17 2:19 ` Arnaldo Carvalho de Melo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170817021930.GA6223@kernel.org \
--to=acme@kernel.org \
--cc=daniel.diaz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox