From: dave.martin@linaro.org (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: vfp: Remote obsolete fpmx_state field from vfp_hard_struct
Date: Wed, 30 Mar 2011 13:46:24 +0100 [thread overview]
Message-ID: <1301489184-4112-2-git-send-email-dave.martin@linaro.org> (raw)
In-Reply-To: <1301489184-4112-1-git-send-email-dave.martin@linaro.org>
The fpmx_state field was presumably used in the past, when
FSTMX/FLDMX were used to save and resture the VFP state.
This was been deprecated since ARMv6, the context switch code
has been ported to use the double-precision load/store variants
many years ago, and now it appears that nothing in the kernel
references this field any more.
Signed-off-by: Dave Martin <dave.martin@linaro.org>
---
arch/arm/include/asm/fpstate.h | 4 ----
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/arch/arm/include/asm/fpstate.h b/arch/arm/include/asm/fpstate.h
index ee5e03e..08bb836 100644
--- a/arch/arm/include/asm/fpstate.h
+++ b/arch/arm/include/asm/fpstate.h
@@ -18,7 +18,6 @@
* VFP storage area has:
* - FPEXC, FPSCR, FPINST and FPINST2.
* - 16 or 32 double precision data registers
- * - an implementation-dependant word of state for FLDMX/FSTMX (pre-ARMv6)
*
* FPEXC will always be non-zero once the VFP has been used in this process.
*/
@@ -29,9 +28,6 @@ struct vfp_hard_struct {
#else
__u64 fpregs[16];
#endif
-#if __LINUX_ARM_ARCH__ < 6
- __u32 fpmx_state;
-#endif
__u32 fpexc;
__u32 fpscr;
/*
--
1.7.1
next prev parent reply other threads:[~2011-03-30 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 12:46 [PATCH] ARM: vfp: Remote obsolete fpmx_state field from vfp_hard_struct Dave Martin
2011-03-30 12:46 ` Dave Martin [this message]
2011-03-30 17:52 ` Russell King - ARM Linux
2011-03-31 9:17 ` Dave Martin
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=1301489184-4112-2-git-send-email-dave.martin@linaro.org \
--to=dave.martin@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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