From: Mathias Krause <minipli@googlemail.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>,
"David S. Miller" <davem@davemloft.net>,
Jesper Nilsson <jesper.nilsson@axis.com>,
Mikael Starvik <starvik@axis.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Mathias Krause <minipli@googlemail.com>,
linux-cris-kernel@axis.com
Subject: [PATCH 5/6] cris: remove unused wp_works_ok macro
Date: Sun, 12 Feb 2017 22:12:11 +0100 [thread overview]
Message-ID: <1486933932-585-6-git-send-email-minipli@googlemail.com> (raw)
In-Reply-To: <1486933932-585-1-git-send-email-minipli@googlemail.com>
It had no use since it's introduction in v2.4.1.2. Get rid of it.
Cc: Jesper Nilsson <jesper.nilsson@axis.com>
Cc: Mikael Starvik <starvik@axis.com>
Signed-off-by: Mathias Krause <minipli@googlemail.com>
---
arch/cris/include/arch-v10/arch/processor.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/cris/include/arch-v10/arch/processor.h b/arch/cris/include/arch-v10/arch/processor.h
index 93feb2a487d8..58f75bee1d6c 100644
--- a/arch/cris/include/arch-v10/arch/processor.h
+++ b/arch/cris/include/arch-v10/arch/processor.h
@@ -7,9 +7,6 @@
*/
#define current_text_addr() ({void *pc; __asm__ ("move.d $pc,%0" : "=rm" (pc)); pc; })
-/* CRIS has no problems with write protection */
-#define wp_works_ok 1
-
/* CRIS thread_struct. this really has nothing to do with the processor itself, since
* CRIS does not do any hardware task-switching, but it's here for legacy reasons.
* The thread_struct here is used when task-switching using _resume defined in entry.S.
--
1.7.10.4
next prev parent reply other threads:[~2017-02-12 21:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 21:12 [PATCH 0/6] struct cpuinfo_x86 related cleanups Mathias Krause
2017-02-12 21:12 ` [PATCH 1/6] x86: drop unneded members of struct cpuinfo_x86 Mathias Krause
2017-02-14 16:17 ` Borislav Petkov
2017-02-14 16:40 ` Mathias Krause
2017-02-14 17:56 ` Geert Uytterhoeven
2017-02-14 18:21 ` Borislav Petkov
2017-02-14 18:46 ` H. Peter Anvin
2017-03-11 13:34 ` [tip:x86/cpu] x86/cpu: Drop " tip-bot for Mathias Krause
2017-02-12 21:12 ` [PATCH 2/6] x86/cpu: drop wp_works_ok member " Mathias Krause
2017-03-11 13:34 ` [tip:x86/cpu] x86/cpu: Drop " tip-bot for Mathias Krause
2017-02-12 21:12 ` [PATCH 3/6] x86/cpu: proc - remove "wp" status line in cpuinfo Mathias Krause
2017-02-14 16:20 ` Borislav Petkov
2017-02-14 16:47 ` Mathias Krause
2017-02-14 17:11 ` Borislav Petkov
2017-02-14 18:13 ` H. Peter Anvin
2017-02-14 18:30 ` Borislav Petkov
2017-02-14 21:42 ` Mathias Krause
2017-02-28 7:15 ` Mathias Krause
2017-02-12 21:12 ` [PATCH 4/6] sparc: remove unused wp_works_ok macro Mathias Krause
2017-02-13 2:48 ` David Miller
2017-02-12 21:12 ` Mathias Krause [this message]
2017-02-13 9:18 ` [PATCH 5/6] cris: " Jesper Nilsson
2017-02-12 21:12 ` [PATCH 6/6] m68k: paging_init - remove dead code Mathias Krause
2017-02-13 9:05 ` Geert Uytterhoeven
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=1486933932-585-6-git-send-email-minipli@googlemail.com \
--to=minipli@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=hpa@zytor.com \
--cc=jesper.nilsson@axis.com \
--cc=linux-cris-kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=starvik@axis.com \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).