From: Segher Boessenkool <segher@kernel.crashing.org>
To: Alistair Popple <alistair@popple.id.au>
Cc: mikey@neuling.org, linuxppc-dev@lists.ozlabs.org, npiggin@gmail.com
Subject: Re: [PATCH 1/2] powerpc: Add base support for ISA v3.1
Date: Fri, 3 Apr 2020 10:32:08 -0500 [thread overview]
Message-ID: <20200403153208.GI26902@gate.crashing.org> (raw)
In-Reply-To: <20200403041055.27535-1-alistair@popple.id.au>
Hi!
On Fri, Apr 03, 2020 at 03:10:54PM +1100, Alistair Popple wrote:
> +#define PCR_ARCH_300 0x10 /* Architecture 3.00 */
It's called 3.0, not 3.00?
Segher
next prev parent reply other threads:[~2020-04-03 15:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 4:10 [PATCH 1/2] powerpc: Add base support for ISA v3.1 Alistair Popple
2020-04-03 4:10 ` [PATCH 2/2] powerpc/dt_cpu_ftrs: Advertise support for ISA v3.1 if selected Alistair Popple
2020-04-03 15:32 ` Segher Boessenkool [this message]
2020-04-21 1:30 ` [PATCH 1/2] powerpc: Add base support for ISA v3.1 Alistair Popple
2020-04-21 1:52 ` Alistair Popple
2020-04-21 1:58 ` Oliver O'Halloran
2020-04-21 17:50 ` Segher Boessenkool
2020-04-21 12:39 ` Michael Ellerman
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=20200403153208.GI26902@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=alistair@popple.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=npiggin@gmail.com \
/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).