From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>, Andrii Nakryiko <andrii@kernel.org>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>, Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Nicolas Schier <nicolas@fjasle.eu>,
Masahiro Yamada <masahiroy@kernel.org>,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
linux-perf-users@vger.kernel.org,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 0/6] Build output clean up
Date: Thu, 17 Nov 2022 12:40:00 -0300 [thread overview]
Message-ID: <Y3ZV0FDW70ADoIYE@kernel.org> (raw)
In-Reply-To: <20221117004356.279422-1-irogers@google.com>
Em Wed, Nov 16, 2022 at 04:43:50PM -0800, Ian Rogers escreveu:
> Reduce build spam from commands not prefixed with @. Make
> install_headers targets distinguishable by adding in the library name
> so:
> INSTALL headers
> becomes:
> INSTALL libapi_headers
>
> Ian Rogers (6):
> tools lib api: clean up install_headers
> tools lib bpf: Avoid install_headers make warning
> tools lib symbol: clean up build output
> tools lib perf: Make install_headers clearer
> tools lib subcmd: Make install_headers clearer
> tools lib traceevent: Make install_headers clearer
Andrii, are you ok with that? Can I carry this on my next (perf/core)
branch?
Testing it now.
- Arnaldo
> tools/lib/api/Makefile | 4 ++--
> tools/lib/bpf/Makefile | 1 +
> tools/lib/perf/Makefile | 2 +-
> tools/lib/subcmd/Makefile | 2 +-
> tools/lib/symbol/Makefile | 4 ++--
> tools/lib/traceevent/Makefile | 4 ++--
> 6 files changed, 9 insertions(+), 8 deletions(-)
>
> --
> 2.38.1.431.g37b22c650d-goog
--
- Arnaldo
next prev parent reply other threads:[~2022-11-17 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 0:43 [PATCH 0/6] Build output clean up Ian Rogers
2022-11-17 0:43 ` [PATCH 1/6] tools lib api: clean up install_headers Ian Rogers
2022-11-17 0:43 ` [PATCH 2/6] tools lib bpf: Avoid install_headers make warning Ian Rogers
2022-11-17 0:43 ` [PATCH 3/6] tools lib symbol: clean up build output Ian Rogers
2022-11-17 0:43 ` [PATCH 4/6] tools lib perf: Make install_headers clearer Ian Rogers
2022-11-17 0:43 ` [PATCH 5/6] tools lib subcmd: " Ian Rogers
2022-11-17 0:43 ` [PATCH 6/6] tools lib traceevent: " Ian Rogers
2022-11-17 15:40 ` Arnaldo Carvalho de Melo [this message]
2022-11-17 19:32 ` [PATCH 0/6] Build output clean up Andrii Nakryiko
2022-11-17 20:12 ` Arnaldo Carvalho de Melo
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=Y3ZV0FDW70ADoIYE@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eranian@google.com \
--cc=haoluo@google.com \
--cc=irogers@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.lau@linux.dev \
--cc=masahiroy@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=peterz@infradead.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.