netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yonghong Song <yhs@fb.com>
To: Andrii Nakryiko <andriin@fb.com>,
	"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Alexei Starovoitov <ast@fb.com>,
	"daniel@iogearbox.net" <daniel@iogearbox.net>
Cc: "andrii.nakryiko@gmail.com" <andrii.nakryiko@gmail.com>,
	Kernel Team <Kernel-team@fb.com>
Subject: Re: [PATCH bpf-next] selftests/bpf: more succinct Makefile output
Date: Tue, 17 Dec 2019 21:54:26 +0000	[thread overview]
Message-ID: <b0e81ae2-9155-e878-1193-3e7ecfab1983@fb.com> (raw)
In-Reply-To: <20191217061425.2346359-1-andriin@fb.com>



On 12/16/19 10:14 PM, Andrii Nakryiko wrote:
> Similarly to bpftool/libbpf output, make selftests/bpf output succinct
> per-item output line. Output is roughly as follows:
> 
> $ make
> ...
>    CLANG-LLC [test_maps] pyperf600.o
>    CLANG-LLC [test_maps] strobemeta.o
>    CLANG-LLC [test_maps] pyperf100.o
>    EXTRA-OBJ [test_progs] cgroup_helpers.o
>    EXTRA-OBJ [test_progs] trace_helpers.o
>       BINARY test_align
>       BINARY test_verifier_log
>     GEN-SKEL [test_progs] fexit_bpf2bpf.skel.h
>     GEN-SKEL [test_progs] test_global_data.skel.h
>     GEN-SKEL [test_progs] sendmsg6_prog.skel.h
> ...
> 
> To see the actual command invocation, verbose mode can be turned on with V=1
> argument:
> 
> $ make V=1
> 
> ... very verbose output ...
> 
> Signed-off-by: Andrii Nakryiko <andriin@fb.com>

Acked-by: Yonghong Song <yhs@fb.com>

  reply	other threads:[~2019-12-17 21:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17  6:14 [PATCH bpf-next] selftests/bpf: more succinct Makefile output Andrii Nakryiko
2019-12-17 21:54 ` Yonghong Song [this message]
2019-12-17 23:22   ` Daniel Borkmann

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=b0e81ae2-9155-e878-1193-3e7ecfab1983@fb.com \
    --to=yhs@fb.com \
    --cc=Kernel-team@fb.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andriin@fb.com \
    --cc=ast@fb.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).