From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 2/5] powerpc: Fix missing CR before {
Date: Wed, 16 Aug 2017 16:01:15 +1000 [thread overview]
Message-ID: <20170816060118.24803-2-benh@kernel.crashing.org> (raw)
In-Reply-To: <20170816060118.24803-1-benh@kernel.crashing.org>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
---
arch/powerpc/kernel/process.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/kernel/process.c b/arch/powerpc/kernel/process.c
index 883216b4296a..14b9a3c46c5d 100644
--- a/arch/powerpc/kernel/process.c
+++ b/arch/powerpc/kernel/process.c
@@ -230,7 +230,8 @@ void enable_kernel_fp(void)
}
EXPORT_SYMBOL(enable_kernel_fp);
-static int restore_fp(struct task_struct *tsk) {
+static int restore_fp(struct task_struct *tsk)
+{
if (tsk->thread.load_fp || msr_tm_active(tsk->thread.regs->msr)) {
load_fp_state(¤t->thread.fp_state);
current->thread.load_fp++;
--
2.13.4
next prev parent reply other threads:[~2017-08-16 6:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 6:01 [PATCH 1/5] powerpc: Test MSR_FP and MSR_VEC when enabling/flushing VSX Benjamin Herrenschmidt
2017-08-16 6:01 ` Benjamin Herrenschmidt [this message]
2017-08-18 12:51 ` [2/5] powerpc: Fix missing CR before { Michael Ellerman
2017-08-16 6:01 ` [PATCH 3/5] powerpc: Remove redundant fp/altivec giveup code Benjamin Herrenschmidt
2017-08-16 6:01 ` [PATCH 4/5] powerpc: Remove redundant clear of MSR_VSX in __giveup_vsx() Benjamin Herrenschmidt
2017-08-16 6:01 ` [PATCH 5/5] powerpc: Remove more redundant VSX save/tests Benjamin Herrenschmidt
2017-08-16 6:02 ` [PATCH 1/5] powerpc: Test MSR_FP and MSR_VEC when enabling/flushing VSX Benjamin Herrenschmidt
2017-08-17 13:03 ` [1/5] " Michael Ellerman
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=20170816060118.24803-2-benh@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).