From: Oliver Upton <oliver.upton@linux.dev>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kvmarm@lists.linux.dev,
Anshuman Khandual <anshuman.khandual@arm.com>,
Shaoqin Huang <shahuang@redhat.com>
Subject: Re: [PATCH v2 0/7] arm64/sysreg: More conversions to automatic generation
Date: Thu, 25 May 2023 21:41:43 +0000 [thread overview]
Message-ID: <ZG/WF22mB4PiJdl4@linux.dev> (raw)
In-Reply-To: <20230419-arm64-syreg-gen-v2-0-4c6add1f6257@kernel.org>
On Tue, May 23, 2023 at 07:36:58PM +0100, Mark Brown wrote:
> Continue working through the register defintions, converting them to
> automatic generation.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> Changes in v2:
> - Also convert OSECCR_EL1, OSDTRRX_EL1 and OSDTRTX_EL1 instead of
> dropping them.
> - Link to v1: https://lore.kernel.org/r/20230419-arm64-syreg-gen-v1-0-936cd769cb9e@kernel.org
>
> ---
> Mark Brown (7):
> arm64/sysreg: Convert MDCCINT_EL1 to automatic register generation
> arm64/sysreg: Convert MDSCR_EL1 to automatic register generation
> arm64/sysreg: Standardise naming of bitfield constants in OSL[AS]R_EL1
> arm64/sysreg: Convert OSLAR_EL1 to automatic generation
> arm64/sysreg: Convert OSDTRRX_EL1 to automatic generation
> arm64/sysreg: Convert OSDTRTX_EL1 to automatic generation
> arm64/sysreg: Convert OSECCR_EL1 to automatic generation
Besides the one comment I had:
Reviewed-by: Oliver Upton <oliver.upton@linux.dev>
I imagine these will go through the arm64 tree right? The KVM diff is
miniscule.
--
Thanks,
Oliver
WARNING: multiple messages have this Message-ID (diff)
From: Oliver Upton <oliver.upton@linux.dev>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kvmarm@lists.linux.dev,
Anshuman Khandual <anshuman.khandual@arm.com>,
Shaoqin Huang <shahuang@redhat.com>
Subject: Re: [PATCH v2 0/7] arm64/sysreg: More conversions to automatic generation
Date: Thu, 25 May 2023 21:41:43 +0000 [thread overview]
Message-ID: <ZG/WF22mB4PiJdl4@linux.dev> (raw)
In-Reply-To: <20230419-arm64-syreg-gen-v2-0-4c6add1f6257@kernel.org>
On Tue, May 23, 2023 at 07:36:58PM +0100, Mark Brown wrote:
> Continue working through the register defintions, converting them to
> automatic generation.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> Changes in v2:
> - Also convert OSECCR_EL1, OSDTRRX_EL1 and OSDTRTX_EL1 instead of
> dropping them.
> - Link to v1: https://lore.kernel.org/r/20230419-arm64-syreg-gen-v1-0-936cd769cb9e@kernel.org
>
> ---
> Mark Brown (7):
> arm64/sysreg: Convert MDCCINT_EL1 to automatic register generation
> arm64/sysreg: Convert MDSCR_EL1 to automatic register generation
> arm64/sysreg: Standardise naming of bitfield constants in OSL[AS]R_EL1
> arm64/sysreg: Convert OSLAR_EL1 to automatic generation
> arm64/sysreg: Convert OSDTRRX_EL1 to automatic generation
> arm64/sysreg: Convert OSDTRTX_EL1 to automatic generation
> arm64/sysreg: Convert OSECCR_EL1 to automatic generation
Besides the one comment I had:
Reviewed-by: Oliver Upton <oliver.upton@linux.dev>
I imagine these will go through the arm64 tree right? The KVM diff is
miniscule.
--
Thanks,
Oliver
_______________________________________________
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:[~2023-05-25 21:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 18:36 [PATCH v2 0/7] arm64/sysreg: More conversions to automatic generation Mark Brown
2023-05-23 18:36 ` Mark Brown
2023-05-23 18:36 ` [PATCH v2 1/7] arm64/sysreg: Convert MDCCINT_EL1 to automatic register generation Mark Brown
2023-05-23 18:36 ` Mark Brown
2023-05-23 18:37 ` [PATCH v2 2/7] arm64/sysreg: Convert MDSCR_EL1 " Mark Brown
2023-05-23 18:37 ` Mark Brown
2023-05-25 21:39 ` Oliver Upton
2023-05-25 21:39 ` Oliver Upton
2023-05-23 18:37 ` [PATCH v2 3/7] arm64/sysreg: Standardise naming of bitfield constants in OSL[AS]R_EL1 Mark Brown
2023-05-23 18:37 ` Mark Brown
2023-05-23 18:37 ` [PATCH v2 4/7] arm64/sysreg: Convert OSLAR_EL1 to automatic generation Mark Brown
2023-05-23 18:37 ` Mark Brown
2023-05-23 18:37 ` [PATCH v2 5/7] arm64/sysreg: Convert OSDTRRX_EL1 " Mark Brown
2023-05-23 18:37 ` Mark Brown
2023-05-30 10:55 ` Shaoqin Huang
2023-05-30 10:55 ` Shaoqin Huang
2023-05-23 18:37 ` [PATCH v2 6/7] arm64/sysreg: Convert OSDTRTX_EL1 " Mark Brown
2023-05-23 18:37 ` Mark Brown
2023-05-30 10:55 ` Shaoqin Huang
2023-05-30 10:55 ` Shaoqin Huang
2023-05-23 18:37 ` [PATCH v2 7/7] arm64/sysreg: Convert OSECCR_EL1 " Mark Brown
2023-05-23 18:37 ` Mark Brown
2023-05-30 10:55 ` Shaoqin Huang
2023-05-30 10:55 ` Shaoqin Huang
2023-05-25 21:41 ` Oliver Upton [this message]
2023-05-25 21:41 ` [PATCH v2 0/7] arm64/sysreg: More conversions " Oliver Upton
2023-06-06 17:30 ` Catalin Marinas
2023-06-06 17:30 ` Catalin Marinas
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=ZG/WF22mB4PiJdl4@linux.dev \
--to=oliver.upton@linux.dev \
--cc=anshuman.khandual@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=shahuang@redhat.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.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.