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 7/7] xtensa: there is no CONFIG_UNALIGNED_USER
Date: Sun, 3 Jul 2011 00:47:52 +0300 [thread overview]
Message-ID: <1309643272-364-8-git-send-email-ext-phil.2.carmody@nokia.com> (raw)
In-Reply-To: <1309643272-364-7-git-send-email-ext-phil.2.carmody@nokia.com>
There is, however, CONFIG_XTENSE_UNALIGNED_USER.
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/xtensa/kernel/traps.c | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/xtensa/kernel/traps.c b/arch/xtensa/kernel/traps.c
index e64efac..993c0dd 100644
--- a/arch/xtensa/kernel/traps.c
+++ b/arch/xtensa/kernel/traps.c
@@ -97,7 +97,7 @@ static dispatch_init_table_t __initdata dispatch_init_table[] = {
/* EXCCAUSE_INTEGER_DIVIDE_BY_ZERO unhandled */
/* EXCCAUSE_PRIVILEGED unhandled */
#if XCHAL_UNALIGNED_LOAD_EXCEPTION || XCHAL_UNALIGNED_STORE_EXCEPTION
-#ifdef CONFIG_UNALIGNED_USER
+#ifdef CONFIG_XTENSA_UNALIGNED_USER
{ EXCCAUSE_UNALIGNED, USER, fast_unaligned },
#else
{ EXCCAUSE_UNALIGNED, 0, do_unaligned_user },
@@ -239,12 +239,12 @@ do_illegal_instruction(struct pt_regs *regs)
/*
* Handle unaligned memory accesses from user space. Kill task.
*
- * If CONFIG_UNALIGNED_USER is not set, we don't allow unaligned memory
+ * If CONFIG_XTENSA_UNALIGNED_USER is not set, we don't allow unaligned memory
* accesses causes from user space.
*/
#if XCHAL_UNALIGNED_LOAD_EXCEPTION || XCHAL_UNALIGNED_STORE_EXCEPTION
-#ifndef CONFIG_UNALIGNED_USER
+#ifndef CONFIG_XTENSA_UNALIGNED_USER
void
do_unaligned_user (struct pt_regs *regs)
{
--
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 ` [PATCH 5/7] ppc: there is no CONFIG_PPC_CPU Phil Carmody
2011-07-02 21:47 ` [PATCH 6/7] nommu: there is no CONFIG_SMALL_TASKS Phil Carmody
2011-07-02 21:47 ` Phil Carmody [this message]
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-8-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®