From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Jens Remus <jremus@linux.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Jan Polensky <japo@linux.ibm.com>,
Thomas Richter <tmricht@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>
Subject: Re: [PATCH v2] perf build: Respect V=1 for Python extension builds
Date: Wed, 10 Jun 2026 17:01:42 -0300 [thread overview]
Message-ID: <ainCpsgwEHLnLnZ-@x1> (raw)
In-Reply-To: <CAP-5=fVWuGKVT+g7RVkQy3zYYWVnHs7Ar76e+-RCJe0ZoZVsug@mail.gmail.com>
On Mon, Jun 08, 2026 at 09:15:36AM -0700, Ian Rogers wrote:
> On Mon, Jun 8, 2026 at 9:06 AM Jens Remus <jremus@linux.ibm.com> wrote:
> >
> > Make util/setup.py respect the verbose build flag (V=1) by conditionally
> > passing --quiet only when not in verbose mode.
> >
> > This eases debugging of Python extension compilation issues and aligns
> > with the existing perf build system behavior.
> >
> > Tested-by: Jan Polensky <japo@linux.ibm.com>
> > Signed-off-by: Jens Remus <jremus@linux.ibm.com>
>
> Reviewed-by: Ian Rogers <irogers@google.com>
Thanks, applied to perf-tools-next, for v7.2.
- Arnaldo
prev parent reply other threads:[~2026-06-10 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 16:06 [PATCH v2] perf build: Respect V=1 for Python extension builds Jens Remus
2026-06-08 16:15 ` Ian Rogers
2026-06-10 20:01 ` 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=ainCpsgwEHLnLnZ-@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=hca@linux.ibm.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=japo@linux.ibm.com \
--cc=jolsa@kernel.org \
--cc=jremus@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tmricht@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox