From: Stephen Zhang <starzhangzsd@gmail.com>
To: tsbogend@alpha.franken.de, liam.howlett@oracle.com,
ebiederm@xmission.com, dbueso@suse.de, alobakin@pm.me,
f.fainelli@gmail.com, paul@crapouillou.net, linux@roeck-us.net,
anemo@mba.ocn.ne.jp
Cc: zhangshida@kylinos.cn, starzhangzsd@gmail.com,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
"Maciej W . Rozycki" <macro@orcam.me.uk>
Subject: [PATCH v2] MIPS: undefine and redefine cpu_has_fpu when it is overrided
Date: Fri, 29 Apr 2022 11:26:21 +0800 [thread overview]
Message-ID: <20220429032621.674865-1-starzhangzsd@gmail.com> (raw)
From: Shida Zhang <zhangshida@kylinos.cn>
Undefine and redefine cpu_has_fpu to 0 when it is overridden with
the "nofpu" option.
Suggested-by: Maciej W. Rozycki <macro@orcam.me.uk>
Signed-off-by: Shida Zhang <zhangshida@kylinos.cn>
---
Changelog in v1 -> v2:
- Choose to redefine cpu_has_fpu to solve the problem.
arch/mips/include/asm/cpu-features.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/mips/include/asm/cpu-features.h b/arch/mips/include/asm/cpu-features.h
index de8cb2ccb781..38eb469008b6 100644
--- a/arch/mips/include/asm/cpu-features.h
+++ b/arch/mips/include/asm/cpu-features.h
@@ -134,6 +134,10 @@
# endif
#else
# define raw_cpu_has_fpu cpu_has_fpu
+# ifndef CONFIG_MIPS_FP_SUPPORT
+# undef cpu_has_fpu
+# define cpu_has_fpu 0
+# endif
#endif
#ifndef cpu_has_32fpr
#define cpu_has_32fpr __isa_ge_or_opt(1, MIPS_CPU_32FPR)
--
2.30.2
next reply other threads:[~2022-04-29 3:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 3:26 Stephen Zhang [this message]
2022-04-29 9:19 ` [PATCH v2] MIPS: undefine and redefine cpu_has_fpu when it is overrided Maciej W. Rozycki
2022-04-29 9:51 ` Thomas Bogendoerfer
2022-04-29 15:11 ` Maciej W. Rozycki
2022-04-30 3:36 ` Stephen Zhang
2022-04-30 15:38 ` Maciej W. Rozycki
2022-05-01 2:54 ` Stephen Zhang
2022-05-01 11:31 ` Maciej W. Rozycki
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=20220429032621.674865-1-starzhangzsd@gmail.com \
--to=starzhangzsd@gmail.com \
--cc=alobakin@pm.me \
--cc=anemo@mba.ocn.ne.jp \
--cc=dbueso@suse.de \
--cc=ebiederm@xmission.com \
--cc=f.fainelli@gmail.com \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=macro@orcam.me.uk \
--cc=paul@crapouillou.net \
--cc=tsbogend@alpha.franken.de \
--cc=zhangshida@kylinos.cn \
/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