From mboxrd@z Thu Jan 1 00:00:00 1970 From: Honnappa Nagarahalli Subject: Correct use of Arm related names Date: Wed, 10 Oct 2018 04:37:08 +0000 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: "Jacob, Jerin" , "Gavin Hu (Arm Technology China)" , Hemant Agrawal , debayang.qdt , Thomas Monjalon To: "dev@dpdk.org" Return-path: Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20053.outbound.protection.outlook.com [40.107.2.53]) by dpdk.org (Postfix) with ESMTP id DA44C1B1FB for ; Wed, 10 Oct 2018 06:37:09 +0200 (CEST) Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi, This email was triggered by a request to change ARM to Arm in the dpdk.org = webpage. I went down the path of finding out the correct names to use. Ther= e has not been consistency in using these names across all other projects. = So, the recommendation I have got is, 'choose something and use it consiste= ntly' (within the DPDK project). Following are my recommendations (please n= otice the lower/upper case of the letters): Architectural State: aarch64/arm64 - referring to aarch64 state - recommended: aarch64 aarch32/arm32 - referring to aarch32 state - recommended: aarch32 (arm32 mi= ght create confusion with armv7) ISA: armv8.x armv7.x Any reference to Company name: Arm So, everything is lower case except when referring to the company (for ex: = Copyright) name. Please let me know if you have any questions. Thank you, Honnappa IMPORTANT NOTICE: The contents of this email and any attachments are confid= ential and may also be privileged. If you are not the intended recipient, p= lease notify the sender immediately and do not disclose the contents to any= other person, use it for any purpose, or store or copy the information in = any medium. Thank you.