From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Gregory CLEMENT <gregory.clement@bootlin.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: [PATCH 2/8] MIPS: regdefs.h: Guard all defines with __ASSEMBLY__
Date: Fri, 09 Feb 2024 18:07:48 +0000 [thread overview]
Message-ID: <20240209-regname-v1-2-2125efa016ef@flygoat.com> (raw)
In-Reply-To: <20240209-regname-v1-0-2125efa016ef@flygoat.com>
Those definitions are only meant to be used in pure assembly code.
Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
---
arch/mips/include/asm/regdef.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/mips/include/asm/regdef.h b/arch/mips/include/asm/regdef.h
index 3c687df1d515..87ba7be1a847 100644
--- a/arch/mips/include/asm/regdef.h
+++ b/arch/mips/include/asm/regdef.h
@@ -14,6 +14,7 @@
#include <asm/sgidefs.h>
+#ifdef __ASSEMBLY__
#if _MIPS_SIM == _MIPS_SIM_ABI32
/*
@@ -102,5 +103,6 @@
#define ra $31 /* return address */
#endif /* _MIPS_SIM == _MIPS_SIM_ABI64 || _MIPS_SIM == _MIPS_SIM_NABI32 */
+#endif /* __ASSEMBLY__ */
#endif /* _ASM_REGDEF_H */
--
2.43.0
next prev parent reply other threads:[~2024-02-09 18:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 18:07 [PATCH 0/8] MIPS: Unify register numbering macros for uasm 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 ` Jiaxun Yang [this message]
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 ` [PATCH 0/8] MIPS: Unify register numbering macros for uasm Thomas Bogendoerfer
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=20240209-regname-v1-2-2125efa016ef@flygoat.com \
--to=jiaxun.yang@flygoat.com \
--cc=gregory.clement@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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®