From: Leo Yan <leo.yan@arm.com>
To: James Clark <james.clark@linaro.org>, Ian Rogers <irogers@google.com>
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>,
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 11:40:54 +0100 [thread overview]
Message-ID: <d2f1b470-fb81-4380-8957-aa56efabf58e@arm.com> (raw)
In-Reply-To: <1e5aa1e1-e5c4-49bb-a43b-a119710a000c@linaro.org>
On 7/16/24 10:10, James Clark wrote:
>> On Mon, Jul 15, 2024 at 7:34 AM Leo Yan <leo.yan@arm.com> wrote:
[...]
>> I think this is objectively worse than just removing the file. It is
>
> Objectively worse is a bit strong. There was some discussion on the
> previous version about the reasoning, but the point is to leave keywords
> so that someone re-writing the NDK docs in the future can find it and
> then the history will be preserved rather than putting it in a new file
> with a new name. Or even someone wondering why their build command
> doesn't work has at least something documented about it, even as a negative.
It is critical for the document not delivering any confusion. Keeping
the doc with a clear clarification, or deleting the useless doc, both
are much better than obsolete info.
> Of course this all depends on whether we decide the Android build
> _should_ be working or not which looks like is also being discussed here.
Yeah, I think the important thing is to get clang/LLVM cross build to
work. This is the prerequisites for using Android NDK.
Thanks,
Leo
prev parent reply other threads:[~2024-07-16 10:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 14:33 [PATCH v2] perf docs: Mark the Android document as obsolete 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
2024-07-15 20:10 ` Leo Yan
2024-07-16 9:10 ` James Clark
2024-07-16 10:40 ` 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=d2f1b470-fb81-4380-8957-aa56efabf58e@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=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