linux-kernel - Re: [PATCH 00/36] AArch64 Linux kernel port

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 10 Jul 2012 22:16:35 +0200
From:	Alexander Holler <holler@...oftware.de>
To:	Joe Perches <joe@...ches.com>
CC:	Catalin Marinas <catalin.marinas@....com>,
	Ingo Molnar <mingo@...nel.org>, Arnd Bergmann <arnd@...db.de>,
	Olof Johansson <olof@...om.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Russell King <linux@....linux.org.uk>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH 00/36] AArch64 Linux kernel port

Am 10.07.2012 19:14, schrieb Joe Perches:
> On Tue, 2012-07-10 at 11:10 +0100, Catalin Marinas wrote:
>> On Tue, Jul 10, 2012 at 08:10:23AM +0100, Ingo Molnar wrote:
>>> * Arnd Bergmann <arnd@...db.de> wrote:
>>>> On Saturday 07 July 2012, Olof Johansson wrote:
>>>>>> ARM introduced AArch64 as part of the ARMv8 architecture
>>>>>
>>>>> With the risk of bikeshedding here, but I find the name awkward. How
>>>>> about just naming the arch port arm64 instead? It's considerably more
>>>>> descriptive in the context of the kernel.  For reference, we didn't
>>>>> name ppc64, nor powerpc, after what the IBM/power.org marketing people
>>>>> were currently calling the architecture at the time either.
>>>>
>>>> I agree the name sucks, [...]
>>>
>>> So why not change it now, when it only bothers a few dozen
>>> people and it is only present in 36 patches? Why go full steam
>>> ahead to annoy thousands of people with it and why spread the
>>> naming madness to thousands of commits?
>>
>> Changing the arch/ dir name is easy at this point. My preference is for
>> consistency with the official name (that cannot be changed) and the gcc
>> triplet. I also don't think it annoys thousands of people, most don't
>> really care. The few reactions I've seen is pretty much because people
>> were expecting arm64 and it came as something else.
>
> Count me as one of the 1000s that think it's a poor name choice.
> I think it's a poor name for marketing purposes too.

Add me to the thousands too.

Using AArch64 is like calling a fly Brachycera or a dog Canis lupus 
familiaris. It might be correct, but it is a name I wouldn't want to use 
when I would need to name the architecture. Try to make a presentation 
where you have to say AArch64 a dozen times. Those two As are imho just 
annoying to speak, besides that AArch64 doesn't given a hint by itself 
that is meant for ARM processors.

And it isn't so that the name will have to be used that seldom, at least 
every distribution would need to use it to name the flavour, like e.g. 
"Fedora AArch64hf" or "Debian AArch64".

Regards,

Alexander
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/