linux-kernel - Re: [PATCH v2] perf docs: Mark the Android document as obsolete

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <d2f1b470-fb81-4380-8957-aa56efabf58e@arm.com>
Date: Tue, 16 Jul 2024 11:40:54 +0100
From: Leo Yan <leo.yan@....com>
To: James Clark <james.clark@...aro.org>, Ian Rogers <irogers@...gle.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
 Namhyung Kim <namhyung@...nel.org>, Jiri Olsa <jolsa@...nel.org>,
 Adrian Hunter <adrian.hunter@...el.com>,
 "Liang, Kan" <kan.liang@...ux.intel.com>,
 Nathan Chancellor <nathan@...nel.org>,
 Nick Desaulniers <ndesaulniers@...gle.com>, Bill Wendling
 <morbo@...gle.com>, Justin Stitt <justinstitt@...gle.com>,
 linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] perf docs: Mark the Android document as obsolete



On 7/16/24 10:10, James Clark wrote:
>> On Mon, Jul 15, 2024 at 7:34 AM Leo Yan <leo.yan@....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