From: Patrick Williams <patrick@stwcx.xyz>
To: Ed Tanous <ed@tanous.net>
Cc: Brad Bishop <bradleyb@fuzziesquirrel.com>,
openbmc <openbmc@lists.ozlabs.org>
Subject: Re: moving meta-{openpower, x86, arm} content to meta-phosphor
Date: Tue, 25 Aug 2020 09:27:54 -0500 [thread overview]
Message-ID: <20200825142754.GJ3532@heinlein> (raw)
In-Reply-To: <CACWQX80NWqfES4vA7M4+jwrfp9Z+HWt=_ni3cMzc4yaw9skekg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
On Fri, Aug 21, 2020 at 09:53:21AM -0700, Ed Tanous wrote:
> On Thu, Aug 20, 2020 at 9:32 AM Patrick Williams <patrick@stwcx.xyz> wrote:
> > 1. What do we do about risc-v which has a dash in the architecture name?
>
> Technically isn't RISC-V the same thing as power9, and we just drop
> the version from it? Or is the "5" an important part of the name?
> RISC-V is definitely a case where having the company in the naming
> convention is going to be important, given that (to my understanding)
> the design can be picked up by anyone and modded as they see fit.
risc-v is the full architecture name, not the chip model name.
Linux has chosen to put it in a 'riscv' subdirectory though, so dropping
the dash seems entirely reasonable.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-08-25 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 13:15 moving meta-{openpower, x86, arm} content to meta-phosphor Brad Bishop
2020-08-20 15:20 ` Supreeth Venkatesh
2020-08-20 16:29 ` Patrick Williams
2020-08-21 16:53 ` Ed Tanous
2020-08-25 14:27 ` Patrick Williams [this message]
2020-08-21 6:20 ` 郁雷
2020-08-21 16:56 ` Ed Tanous
2020-08-21 16:31 ` Ed Tanous
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=20200825142754.GJ3532@heinlein \
--to=patrick@stwcx.xyz \
--cc=bradleyb@fuzziesquirrel.com \
--cc=ed@tanous.net \
--cc=openbmc@lists.ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.