DPDK patches and discussions
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Jacob,  Jerin" <Jerin.JacobKollanukkaran@cavium.com>,
	"Gavin Hu (Arm Technology China)" <Gavin.Hu@arm.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	debayang.qdt <debayang.qdt@qualcommdatacenter.com>,
	 Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] Correct use of Arm related names
Date: Wed, 10 Oct 2018 04:37:08 +0000	[thread overview]
Message-ID: <AM6PR08MB3672075F241CEAA02C6CF58F98E00@AM6PR08MB3672.eurprd08.prod.outlook.com> (raw)

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. There has not been consistency in using these names across all other projects. So, the recommendation I have got is, 'choose something and use it consistently' (within the DPDK project). Following are my recommendations (please notice 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 might 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 confidential and may also be privileged. If you are not the intended recipient, please 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.

             reply	other threads:[~2018-10-10  4:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10  4:37 Honnappa Nagarahalli [this message]
2018-10-10  4:39 ` Honnappa Nagarahalli
2018-10-10  8:48 ` Thomas Monjalon

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=AM6PR08MB3672075F241CEAA02C6CF58F98E00@AM6PR08MB3672.eurprd08.prod.outlook.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=Gavin.Hu@arm.com \
    --cc=Jerin.JacobKollanukkaran@cavium.com \
    --cc=debayang.qdt@qualcommdatacenter.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=thomas@monjalon.net \
    /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;
as well as URLs for NNTP newsgroup(s).