From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Clark Williams <williams@redhat.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
James Clark <james.clark@linaro.org>,
Quentin Monnet <qmo@kernel.org>
Subject: [PATCH 0/2] Fast path feature detection fixes
Date: Wed, 11 Dec 2024 19:45:07 -0300 [thread overview]
Message-ID: <20241211224509.797827-1-acme@kernel.org> (raw)
Hi,
This is on top of a previous patch I sent today for libunwind
opt-in fallout, I'll continue checking if what is being enabled when
test-all.c builds is the right set of features to be declared as
detected on this fast path method.
- Arnaldo
Arnaldo Carvalho de Melo (2):
tools build feature: Add some comments to explain the FEATURE_TESTS logic
tools build feature: Don't set feature-libcap=1 if libcap-devel isn't available
tools/build/Makefile.feature | 37 ++++++++++++++++++++++++++++++++++--
tools/build/feature/Makefile | 2 +-
2 files changed, 36 insertions(+), 3 deletions(-)
--
2.47.0
next reply other threads:[~2024-12-11 22:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 22:45 Arnaldo Carvalho de Melo [this message]
2024-12-11 22:45 ` [PATCH 1/2] tools build feature: Add some comments to explain the FEATURE_TESTS logic Arnaldo Carvalho de Melo
2024-12-12 4:24 ` Ian Rogers
2024-12-11 22:45 ` [PATCH 2/2] tools build feature: Don't set feature-libcap=1 if libcap-devel isn't available Arnaldo Carvalho de Melo
2024-12-12 4:25 ` Ian Rogers
2024-12-12 10:16 ` Quentin Monnet
2024-12-12 18:32 ` 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=20241211224509.797827-1-acme@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=qmo@kernel.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.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.