From: Jackie Liu <liu.yun@linux.dev>
To: Huacai Chen <chenhc@lemote.com>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
"open list:MIPS" <linux-mips@vger.kernel.org>
Subject: Re: [PATCH] MIPS: loongson64: make LOONGSON64 depends on MIPS_FP_SUPPORT
Date: Mon, 13 Sep 2021 11:46:14 +0800 [thread overview]
Message-ID: <ce0ab59f-2fc8-6ec0-3cdf-a11ff235990f@linux.dev> (raw)
In-Reply-To: <CAAhV-H4=JGWencuHrYmFTC1Dh1KFapawW-UZdhZGM0gu-h3Akw@mail.gmail.com>
Hi, Huacai.
在 2021/9/13 上午10:59, Huacai Chen 写道:
> Hi, Jackie,
>
> On Mon, Sep 13, 2021 at 10:42 AM Jackie Liu <liu.yun@linux.dev> wrote:
>>
>> From: Jackie Liu <liuyun01@kylinos.cn>
>>
>> mach/loongson64 fails to build when the FPU support is disabled:
>>
>> arch/mips/loongson64/cop2-ex.c:45:15: error: implicit declaration of function ‘__is_fpu_owner’; did you mean ‘is_fpu_owner’? [-Werror=implicit-function-declaration]
>> arch/mips/loongson64/cop2-ex.c:98:30: error: ‘struct thread_struct’ has no member named ‘fpu’
>> arch/mips/loongson64/cop2-ex.c:99:30: error: ‘struct thread_struct’ has no member named ‘fpu’
>> arch/mips/loongson64/cop2-ex.c:131:43: error: ‘struct thread_struct’ has no member named ‘fpu’
>> arch/mips/loongson64/cop2-ex.c:137:38: error: ‘struct thread_struct’ has no member named ‘fpu’
>> arch/mips/loongson64/cop2-ex.c:203:30: error: ‘struct thread_struct’ has no member named ‘fpu’
>> arch/mips/loongson64/cop2-ex.c:219:30: error: ‘struct thread_struct’ has no member named ‘fpu’
>> arch/mips/loongson64/cop2-ex.c:283:38: error: ‘struct thread_struct’ has no member named ‘fpu’
>> arch/mips/loongson64/cop2-ex.c:301:38: error: ‘struct thread_struct’ has no member named ‘fpu’
>>
>> Fixes: ef2f826c8f2f ("MIPS: Loongson-3: Enable the COP2 usage")
> I suggest moving this config option to CPU_LOONGSON64.
Looks correct, thanks for the suggestion.
--
Jackie Liu
>
> Huacai
>
>> Reported-by: k2ci robot <kernel-bot@kylinos.cn>
>> Signed-off-by: Jackie Liu <liuyun01@kylinos.cn>
>> ---
>> arch/mips/Kconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
>> index 24e374266fdc..1164c32fd87b 100644
>> --- a/arch/mips/Kconfig
>> +++ b/arch/mips/Kconfig
>> @@ -487,6 +487,7 @@ config MACH_LOONGSON64
>> select ISA
>> select I8259
>> select IRQ_MIPS_CPU
>> + select MIPS_FP_SUPPORT
>> select NO_EXCEPT_FILL
>> select NR_CPUS_DEFAULT_64
>> select USE_GENERIC_EARLY_PRINTK_8250
>> --
>> 2.25.1
>>
prev parent reply other threads:[~2021-09-13 3:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 2:41 [PATCH] MIPS: loongson64: make LOONGSON64 depends on MIPS_FP_SUPPORT Jackie Liu
2021-09-13 2:59 ` Huacai Chen
2021-09-13 3:46 ` Jackie Liu [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=ce0ab59f-2fc8-6ec0-3cdf-a11ff235990f@linux.dev \
--to=liu.yun@linux.dev \
--cc=chenhc@lemote.com \
--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;
as well as URLs for NNTP newsgroup(s).