From: sunying@nj.iscas.ac.cn
To: linux-csky@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, 侯朋朋 <pengpeng@iscas.ac.cn>,
renyanjie01@gmail.com
Subject: arch/csky/abiv2/inc/abi/fpu.h with a series of the non-existing config "OPEN_FPU_xxx"
Date: Tue, 12 Sep 2023 16:03:56 +0800 (GMT+08:00) [thread overview]
Message-ID: <7afcf320.5c2f1.18a886b202f.Coremail.sunying@nj.iscas.ac.cn> (raw)
In the header file arch/csky/abiv2/inc/abi/fpu.h, lines 30-64 refer to
a series of configuration options starting with "OPEN_FPU" for conditional compilation,
but these configuration options are not defined in any kconfig files,
which means the "#ifdef CONFIG_OPEN_FPU_xxx" condition contains dead code.
Do these configuration options need to be retained and added later? Or can we simply drop the dead code?
Best regards,
Yanjie Ren
Ying Sun
reply other threads:[~2023-09-12 8:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7afcf320.5c2f1.18a886b202f.Coremail.sunying@nj.iscas.ac.cn \
--to=sunying@nj.iscas.ac.cn \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pengpeng@iscas.ac.cn \
--cc=renyanjie01@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).