From: Leo Yan <leo.yan@arm.com>
To: James Clark <james.clark@linaro.org>, Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"Liang, Kan" <kan.liang@linux.intel.com>,
Nick Terrell <terrelln@fb.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Thomas Richter <tmricht@linux.ibm.com>,
Changbin Du <changbin.du@huawei.com>,
amadio@gentoo.org, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v3 7/7] perf docs: Remove the Android cross building document
Date: Mon, 15 Jul 2024 15:48:09 +0100 [thread overview]
Message-ID: <b58e3d55-5fa2-451a-8196-b5a031805946@arm.com> (raw)
In-Reply-To: <83301e3e-e049-4af4-9f0b-29bdfc201543@linaro.org>
On 7/12/24 14:38, James Clark wrote:
[...]
>> Given the test result, my conclusion is the doc for Android cross building
>> is not useful for a long while. If we really want to support it, I would
>> like to suggest to take a separate task for fixing LLVM / Clang cross
>> compilation.
>
> We could replace the entire contents of the file with something like
> "Android NDK compilation deprecated -- no longer supported". It might
> help someone in being able to recover the history of the file by leaving
> in some keywords. If you delete it it becomes very unlikely that the
> history will be found by someone trying to get it working again.
A specific Android version has corresponding Linux kernels. It is likely
developers can find what they want, as they should work on an relative
old kernel source tree.
Given Namhyung and you both are concerned for removing the doc, I have
followed the suggestion, respined this patch and sent sepearately [1],
as this patch is not really related to cross building fix.
Thanks,
Leo
[1]
https://lore.kernel.org/linux-perf-users/20240715143342.52236-1-leo.yan@arm.com/T/#u
prev parent reply other threads:[~2024-07-15 14:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-06 18:29 [PATCH v3 0/7] perf: build: Fix cross compilation Leo Yan
2024-07-06 18:29 ` [PATCH v3 1/7] perf: build: Setup PKG_CONFIG_LIBDIR for " Leo Yan
2024-07-12 4:52 ` Namhyung Kim
2024-07-12 10:13 ` Leo Yan
2024-07-06 18:29 ` [PATCH v3 2/7] perf: build: Set Python configuration " Leo Yan
2024-07-06 18:29 ` [PATCH v3 3/7] perf: build: Only link libebl.a for old libdw Leo Yan
2024-07-06 18:29 ` [PATCH v3 4/7] perf: build: Link lib 'lzma' for static build Leo Yan
2024-07-06 18:29 ` [PATCH v3 5/7] perf: build: Link lib 'zstd' " Leo Yan
2024-07-06 18:29 ` [PATCH v3 6/7] perf docs: Document cross compilation Leo Yan
2024-07-06 18:29 ` [PATCH v3 7/7] perf docs: Remove the Android cross building document Leo Yan
2024-07-12 4:58 ` Namhyung Kim
2024-07-12 5:37 ` Ian Rogers
2024-07-12 11:02 ` Leo Yan
2024-07-12 13:38 ` James Clark
2024-07-15 14:48 ` Leo Yan [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=b58e3d55-5fa2-451a-8196-b5a031805946@arm.com \
--to=leo.yan@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=amadio@gentoo.org \
--cc=changbin.du@huawei.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=mark.rutland@arm.com \
--cc=morbo@google.com \
--cc=namhyung@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=terrelln@fb.com \
--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