From: Phil Carmody <ext-phil.2.carmody@nokia.com>
To: trivial@kernel.org
Cc: ext-phil.2.carmody@nokia.com, linux-kernel@vger.kernel.org
Subject: [PATCH 5/7] ppc: there is no CONFIG_PPC_CPU
Date: Sun, 3 Jul 2011 00:47:50 +0300 [thread overview]
Message-ID: <1309643272-364-6-git-send-email-ext-phil.2.carmody@nokia.com> (raw)
In-Reply-To: <1309643272-364-5-git-send-email-ext-phil.2.carmody@nokia.com>
There is, however, CONFIG_PPC_FPU. Seems to be a typo introduced
in cd64d1697cf079bb8a67766e36e88ced38498933.
Part of a shotgun patchset; found by greps, seds, and diffs
rather than actual understanding.
Signed-off-by: Phil Carmody <ext-phil.2.carmody@nokia.com>
---
arch/powerpc/lib/sstep.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/lib/sstep.c b/arch/powerpc/lib/sstep.c
index 9a52349..e3b28e3 100644
--- a/arch/powerpc/lib/sstep.c
+++ b/arch/powerpc/lib/sstep.c
@@ -1395,7 +1395,7 @@ int __kprobes emulate_step(struct pt_regs *regs, unsigned int instr)
regs->gpr[rd] = byterev_4(val);
goto ldst_done;
-#ifdef CONFIG_PPC_CPU
+#ifdef CONFIG_PPC_FPU
case 535: /* lfsx */
case 567: /* lfsux */
if (!(regs->msr & MSR_FP))
--
1.7.2.5
next prev parent reply other threads:[~2011-07-02 21:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-02 21:47 [PATCH 0/7] [TRIVIAL] Cleanup spurious CONFIGs Phil Carmody
2011-07-02 21:47 ` [PATCH 1/7] mn10300: there is no CONFIG_CALIBRATE_DELAY Phil Carmody
2011-07-02 21:47 ` [PATCH 2/7] cris: there is no CONFIG_ETRAX_KGB_PORT2 Phil Carmody
2011-07-02 21:47 ` [PATCH 3/7] xfs: there is no CONFIG_KDB_MODULES Phil Carmody
2011-07-02 21:47 ` [PATCH 4/7] ppc: there is no CONFIG_PPC47x Phil Carmody
2011-07-02 21:47 ` Phil Carmody [this message]
2011-07-02 21:47 ` [PATCH 6/7] nommu: there is no CONFIG_SMALL_TASKS Phil Carmody
2011-07-02 21:47 ` [PATCH 7/7] xtensa: there is no CONFIG_UNALIGNED_USER Phil Carmody
2011-07-04 4:58 ` [PATCH 3/7] xfs: there is no CONFIG_KDB_MODULES Dave Chinner
2011-07-04 8:51 ` Phil Carmody
2011-07-04 13:15 ` Lukasz
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=1309643272-364-6-git-send-email-ext-phil.2.carmody@nokia.com \
--to=ext-phil.2.carmody@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.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
all inboxes | Powered by JetHome®