From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: Gregory CLEMENT <gregory.clement@bootlin.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] MIPS: Unify register numbering macros for uasm
Date: Tue, 20 Feb 2024 14:39:40 +0100 [thread overview]
Message-ID: <ZdSrnG493wn2U+5s@alpha.franken.de> (raw)
In-Reply-To: <20240209-regname-v1-0-2125efa016ef@flygoat.com>
On Fri, Feb 09, 2024 at 06:07:46PM +0000, Jiaxun Yang wrote:
> Hi all,
>
> This is a attempt to unify register numbering macros for uasm,
> in response to review comment [1].
>
> This is a rather large cosmetic change so I decided to send
> it as a sepreate set.
>
> Please review.
> Thanks
>
> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
> ---
> Jiaxun Yang (8):
> MIPS: Unify define of CP0 registers for uasm code
> MIPS: regdefs.h: Guard all defines with __ASSEMBLY__
> MIPS: regdefs.h: Define a set of register numbers
> MIPS: traps: Use GPR number macros
> MIPS: page: Use GPR number macros
> MIPS: tlbex: Use GPR number macros
> MIPS: kvm/entry: Use GPR number macros
> MIPS: pm-cps: Use GPR number macros
>
> arch/mips/include/asm/mipsregs.h | 249 +++++++++++++++++-----
> arch/mips/include/asm/regdef.h | 91 +++++++++
> arch/mips/kernel/pm-cps.c | 134 ++++++------
> arch/mips/kernel/traps.c | 6 +-
> arch/mips/kvm/entry.c | 431 +++++++++++++++++----------------------
> arch/mips/mm/page.c | 202 +++++++++---------
> arch/mips/mm/tlbex.c | 214 +++++++++----------
> 7 files changed, 737 insertions(+), 590 deletions(-)
> ---
> base-commit: 445a555e0623387fa9b94e68e61681717e70200a
> change-id: 20240209-regname-4c14f1147e25
series applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2024-02-20 13:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 18:07 Jiaxun Yang
2024-02-09 18:07 ` [PATCH 1/8] MIPS: Unify define of CP0 registers for uasm code Jiaxun Yang
2024-02-09 18:07 ` [PATCH 2/8] MIPS: regdefs.h: Guard all defines with __ASSEMBLY__ Jiaxun Yang
2024-02-09 18:07 ` [PATCH 3/8] MIPS: regdefs.h: Define a set of register numbers Jiaxun Yang
2024-02-09 18:07 ` [PATCH 4/8] MIPS: traps: Use GPR number macros Jiaxun Yang
2024-02-09 18:07 ` [PATCH 5/8] MIPS: page: " Jiaxun Yang
2024-02-09 18:07 ` [PATCH 6/8] MIPS: tlbex: " Jiaxun Yang
2024-02-09 18:07 ` [PATCH 7/8] MIPS: kvm/entry: " Jiaxun Yang
2024-02-09 18:07 ` [PATCH 8/8] MIPS: pm-cps: " Jiaxun Yang
2024-02-20 13:39 ` Thomas Bogendoerfer [this message]
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=ZdSrnG493wn2U+5s@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=gregory.clement@bootlin.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®