From: Paul Bolle <pebolle@tiscali.nl>
To: Thomas Gleixner <tglx@linutronix.de>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux390@de.ibm.com, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] locking: remove three unused Kconfig symbols
Date: Mon, 08 Apr 2013 15:35:54 +0200 [thread overview]
Message-ID: <1365428154.1830.99.camel@x61.thuisdomein> (raw)
The Kconfig symbols ARCH_INLINE_READ_UNLOCK_IRQ,
ARCH_INLINE_SPIN_UNLOCK_IRQ, and ARCH_INLINE_WRITE_UNLOCK_IRQ were added
in v2.6.33, but have never actually been used. It is safe to remove
these.
Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
---
Untested. These three symbols were added in commit
6beb000923882f6204ea2cfcd932e568e900803f ("locking: Make inlining
decision Kconfig based").
arch/s390/Kconfig | 3 ---
kernel/Kconfig.locks | 10 ----------
2 files changed, 13 deletions(-)
diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig
index eb8fb62..8c544d2 100644
--- a/arch/s390/Kconfig
+++ b/arch/s390/Kconfig
@@ -70,7 +70,6 @@ config S390
select ARCH_INLINE_READ_TRYLOCK
select ARCH_INLINE_READ_UNLOCK
select ARCH_INLINE_READ_UNLOCK_BH
- select ARCH_INLINE_READ_UNLOCK_IRQ
select ARCH_INLINE_READ_UNLOCK_IRQRESTORE
select ARCH_INLINE_SPIN_LOCK
select ARCH_INLINE_SPIN_LOCK_BH
@@ -80,7 +79,6 @@ config S390
select ARCH_INLINE_SPIN_TRYLOCK_BH
select ARCH_INLINE_SPIN_UNLOCK
select ARCH_INLINE_SPIN_UNLOCK_BH
- select ARCH_INLINE_SPIN_UNLOCK_IRQ
select ARCH_INLINE_SPIN_UNLOCK_IRQRESTORE
select ARCH_INLINE_WRITE_LOCK
select ARCH_INLINE_WRITE_LOCK_BH
@@ -89,7 +87,6 @@ config S390
select ARCH_INLINE_WRITE_TRYLOCK
select ARCH_INLINE_WRITE_UNLOCK
select ARCH_INLINE_WRITE_UNLOCK_BH
- select ARCH_INLINE_WRITE_UNLOCK_IRQ
select ARCH_INLINE_WRITE_UNLOCK_IRQRESTORE
select ARCH_SAVE_PAGE_KEYS if HIBERNATION
select ARCH_WANT_IPC_PARSE_VERSION
diff --git a/kernel/Kconfig.locks b/kernel/Kconfig.locks
index 44511d1..c438507 100644
--- a/kernel/Kconfig.locks
+++ b/kernel/Kconfig.locks
@@ -25,9 +25,6 @@ config ARCH_INLINE_SPIN_UNLOCK
config ARCH_INLINE_SPIN_UNLOCK_BH
bool
-config ARCH_INLINE_SPIN_UNLOCK_IRQ
- bool
-
config ARCH_INLINE_SPIN_UNLOCK_IRQRESTORE
bool
@@ -53,13 +50,9 @@ config ARCH_INLINE_READ_UNLOCK
config ARCH_INLINE_READ_UNLOCK_BH
bool
-config ARCH_INLINE_READ_UNLOCK_IRQ
- bool
-
config ARCH_INLINE_READ_UNLOCK_IRQRESTORE
bool
-
config ARCH_INLINE_WRITE_TRYLOCK
bool
@@ -81,9 +74,6 @@ config ARCH_INLINE_WRITE_UNLOCK
config ARCH_INLINE_WRITE_UNLOCK_BH
bool
-config ARCH_INLINE_WRITE_UNLOCK_IRQ
- bool
-
config ARCH_INLINE_WRITE_UNLOCK_IRQRESTORE
bool
--
1.7.11.7
next reply other threads:[~2013-04-08 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 13:35 Paul Bolle [this message]
2013-04-08 15:16 ` [PATCH] locking: remove three unused Kconfig symbols Ingo Molnar
2013-04-08 15:30 ` Paul Bolle
2013-04-08 15:32 ` Paul Bolle
2013-04-08 15:36 ` Ingo Molnar
2013-05-17 8:51 ` [PATCH v2] locking: Fix copy/paste errors "ARCH_INLINE_*_UNLOCK_BH" Paul Bolle
2013-05-17 10:18 ` Peter Zijlstra
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=1365428154.1830.99.camel@x61.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=a.p.zijlstra@chello.nl \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=mingo@elte.hu \
--cc=schwidefsky@de.ibm.com \
--cc=tglx@linutronix.de \
/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