From: Mark Brown <broonie@kernel.org>
To: James Morse <james.morse@arm.com>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 36/38] arm64/sysreg: Convert ID_AFR0_EL1 to automatic generation
Date: Mon, 3 Oct 2022 17:28:05 +0100 [thread overview]
Message-ID: <YzsNlc57mimnJzBA@sirena.org.uk> (raw)
In-Reply-To: <20220930140211.3215348-37-james.morse@arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 205 bytes --]
On Fri, Sep 30, 2022 at 03:02:09PM +0100, James Morse wrote:
> Convert ID_AFR0_EL1 to be automatically generated as per DDI04187H.a,
> no functional changes.
Reviewed-by: Mark Brown <broonie@kernel.org>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-10-03 16:29 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 14:01 [RFC PATCH 00/38] arm64/sysreg: Convert aarch32 id regs James Morse
2022-09-30 14:01 ` [RFC PATCH 01/38] arm64/sysreg: Standardise naming for ID_MMFR0_EL1 James Morse
2022-09-30 14:01 ` [RFC PATCH 02/38] arm64/sysreg: Standardise naming for ID_MMFR4_EL1 James Morse
2022-09-30 14:01 ` [RFC PATCH 03/38] arm64/sysreg: Standardise naming for ID_MMFR5_EL1 James Morse
2022-09-30 14:01 ` [RFC PATCH 04/38] arm64/sysreg: Standardise naming for ID_ISAR0_EL1 James Morse
2022-09-30 14:01 ` [RFC PATCH 05/38] arm64/sysreg: Standardise naming for ID_ISAR4_EL1 James Morse
2022-09-30 14:01 ` [RFC PATCH 06/38] arm64/sysreg: Standardise naming for ID_ISAR5_EL1 James Morse
2022-09-30 14:01 ` [RFC PATCH 07/38] arm64/sysreg: Standardise naming for ID_ISAR6_EL1 James Morse
2022-09-30 14:01 ` [RFC PATCH 08/38] arm64/sysreg: Standardise naming for ID_PFR0_EL1 James Morse
2022-09-30 14:01 ` [RFC PATCH 09/38] arm64/sysreg: Standardise naming for ID_PFR1_EL1 James Morse
2022-09-30 14:01 ` [RFC PATCH 10/38] arm64/sysreg: Standardise naming for ID_PFR2_EL1 James Morse
2022-09-30 14:01 ` [RFC PATCH 11/38] arm64/sysreg: Standardise naming for ID_DFR0_EL1 James Morse
2022-09-30 14:01 ` [RFC PATCH 12/38] arm64/sysreg: Standardise naming for ID_DFR1_EL1 James Morse
2022-09-30 14:01 ` [RFC PATCH 13/38] arm64/sysreg: Standardise naming for MVFR0_EL1 James Morse
2022-09-30 14:01 ` [RFC PATCH 14/38] arm64/sysreg: Standardise naming for MVFR1_EL1 James Morse
2022-09-30 14:01 ` [RFC PATCH 15/38] arm64/sysreg: Standardise naming for MVFR2_EL1 James Morse
2022-09-30 14:01 ` [RFC PATCH 16/38] arm64/sysreg: Extend the maximum width of a register and symbole name James Morse
2022-10-03 15:30 ` Mark Brown
2022-09-30 14:01 ` [RFC PATCH 17/38] arm64/sysreg: Convert ID_MMFR0_EL1 to automatic generation James Morse
2022-10-03 15:34 ` Mark Brown
2022-09-30 14:01 ` [RFC PATCH 18/38] arm64/sysreg: Convert ID_MMFR1_EL1 " James Morse
2022-10-03 15:37 ` Mark Brown
2022-09-30 14:01 ` [RFC PATCH 19/38] arm64/sysreg: Convert ID_MMFR2_EL1 " James Morse
2022-10-03 15:43 ` Mark Brown
2022-09-30 14:01 ` [RFC PATCH 20/38] arm64/sysreg: Convert ID_MMFR3_EL1 " James Morse
2022-10-03 15:46 ` Mark Brown
2022-09-30 14:01 ` [RFC PATCH 21/38] arm64/sysreg: Convert ID_MMFR4_EL1 " James Morse
2022-10-03 15:48 ` Mark Brown
2022-09-30 14:01 ` [RFC PATCH 22/38] arm64/sysreg: Convert ID_ISAR0_EL1 " James Morse
2022-10-03 15:51 ` Mark Brown
2022-09-30 14:01 ` [RFC PATCH 23/38] arm64/sysreg: Convert ID_ISAR1_EL1 " James Morse
2022-10-03 15:53 ` Mark Brown
2022-09-30 14:01 ` [RFC PATCH 24/38] arm64/sysreg: Convert ID_ISAR2_EL1 " James Morse
2022-10-03 15:58 ` Mark Brown
2022-09-30 14:01 ` [RFC PATCH 25/38] arm64/sysreg: Convert ID_ISAR3_EL1 " James Morse
2022-10-03 16:04 ` Mark Brown
2022-09-30 14:01 ` [RFC PATCH 26/38] arm64/sysreg: Convert ID_ISAR4_EL1 " James Morse
2022-10-03 16:07 ` Mark Brown
2022-09-30 14:02 ` [RFC PATCH 27/38] arm64/sysreg: Convert ID_ISAR5_EL1 " James Morse
2022-10-03 16:10 ` Mark Brown
2022-09-30 14:02 ` [RFC PATCH 28/38] arm64/sysreg: Convert ID_ISAR6_EL1 " James Morse
2022-10-03 16:11 ` Mark Brown
2022-09-30 14:02 ` [RFC PATCH 29/38] arm64/sysreg: Convert ID_PFR0_EL1 " James Morse
2022-10-03 16:14 ` Mark Brown
2022-09-30 14:02 ` [RFC PATCH 30/38] arm64/sysreg: Convert ID_PFR1_EL1 " James Morse
2022-10-03 16:16 ` Mark Brown
2022-09-30 14:02 ` [RFC PATCH 31/38] arm64/sysreg: Convert ID_PFR2_EL1 " James Morse
2022-10-03 16:17 ` Mark Brown
2022-09-30 14:02 ` [RFC PATCH 32/38] arm64/sysreg: Convert MVFR0_EL1 " James Morse
2022-10-03 16:19 ` Mark Brown
2022-09-30 14:02 ` [RFC PATCH 33/38] arm64/sysreg: Convert MVFR1_EL1 " James Morse
2022-10-03 16:21 ` Mark Brown
2022-09-30 14:02 ` [RFC PATCH 34/38] arm64/sysreg: Convert MVFR2_EL1 " James Morse
2022-10-03 16:25 ` Mark Brown
2022-09-30 14:02 ` [RFC PATCH 35/38] arm64/sysreg: Convert ID_MMFR5_EL1 " James Morse
2022-10-03 16:27 ` Mark Brown
2022-09-30 14:02 ` [RFC PATCH 36/38] arm64/sysreg: Convert ID_AFR0_EL1 " James Morse
2022-10-03 16:28 ` Mark Brown [this message]
2022-09-30 14:02 ` [RFC PATCH 37/38] arm64/sysreg: Convert ID_DFR0_EL1 " James Morse
2022-10-03 16:30 ` Mark Brown
2022-09-30 14:02 ` [RFC PATCH 38/38] arm64/sysreg: Convert ID_DFR1_EL1 " James Morse
2022-10-03 16:32 ` Mark Brown
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=YzsNlc57mimnJzBA@sirena.org.uk \
--to=broonie@kernel.org \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 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).