From: Leo Yan <leo.yan@arm.com>
To: Ian Rogers <irogers@google.com>, llvm@lists.linux.dev
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
"Liang, Kan" <kan.liang@linux.intel.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
James Clark <james.clark@linaro.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] perf docs: Mark the Android document as obsolete
Date: Tue, 16 Jul 2024 16:41:55 +0100 [thread overview]
Message-ID: <88887095-fd7d-4428-b96f-27e18b547b2c@arm.com> (raw)
In-Reply-To: <CAP-5=fVvg=5SE29_SUW0MWmLADL477vpP2DBid2kKZ8kNqxXiA@mail.gmail.com>
On 7/16/2024 4:05 PM, Ian Rogers wrote:
[...]
>>> I'm not sure how we detect
>>> in the build that we're using clang, I suspect there is an approach in
>>> a different kernel Makefile/Build that already tackles this but my
>>> quick searching didn't yield anything - perhaps the change would be
>>> better suited to the location the CROSS_COMPILE prefix is added to
>>> gcc.
>>
>> Should we follow up the steps in the Documentation/kbuild/llvm.rst?
>> The document uses the flag 'LLVM=1' for selecting LLVM/Clang.
>
> Fix clang-built-linux email to llvm@lists.linux.dev
>
> I'm not sure as the kernel build and the tools build differ in certain
> ways. Perhaps look at the selftests build to see what they do, as they
> are under tools and share the build files.
Okay. thanks for suggestion.
Leo
next prev parent reply other threads:[~2024-07-16 15:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 14:33 Leo Yan
2024-07-15 15:29 ` James Clark
2024-07-15 17:17 ` Ian Rogers
2024-07-15 19:31 ` Leo Yan
2024-07-15 19:44 ` Ian Rogers
2024-07-15 20:06 ` Ian Rogers
2024-07-15 20:36 ` Leo Yan
2024-07-15 21:21 ` Ian Rogers
2024-07-16 10:06 ` Leo Yan
2024-07-16 13:30 ` Ian Rogers
2024-07-16 13:49 ` Leo Yan
2024-07-16 15:05 ` Ian Rogers
2024-07-16 15:41 ` Leo Yan [this message]
2024-07-15 20:10 ` Leo Yan
2024-07-16 9:10 ` James Clark
2024-07-16 10:40 ` Leo Yan
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=88887095-fd7d-4428-b96f-27e18b547b2c@arm.com \
--to=leo.yan@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=justinstitt@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=namhyung@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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
all inboxes | Powered by JetHome®