From: Paul Bolle <pebolle@tiscali.nl>
To: Richard Kuo <rkuo@codeaurora.org>, Jonas Bonn <jonas@southpole.se>
Cc: linux-hexagon@vger.kernel.org, linux@openrisc.net,
linux-kernel@vger.kernel.org
Subject: [PATCH] [RESEND] arch: remove CONFIG_GENERIC_FIND_NEXT_BIT again
Date: Sat, 30 Mar 2013 10:06:06 +0100 [thread overview]
Message-ID: <1364634366.1345.111.camel@x61.thuisdomein> (raw)
In-Reply-To: <51545BFB.9010806@southpole.se>
CONFIG_GENERIC_FIND_NEXT_BIT was removed in v3.0, but reappeared in two
architectures. Remove it again.
Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
Acked-by: Jonas Bonn <jonas@southpole.se>
---
0) Richard asked (off list) to resend. There appear to be problems
locating the patch in the archives for LKML and/or linux-hexagon.
1) Added Jonas' ACK. Richard will pull the patch in a hexagon tree and
handle it from there.
arch/hexagon/Kconfig | 3 ---
arch/openrisc/Kconfig | 3 ---
2 files changed, 6 deletions(-)
diff --git a/arch/hexagon/Kconfig b/arch/hexagon/Kconfig
index 48130eb..650ef81 100644
--- a/arch/hexagon/Kconfig
+++ b/arch/hexagon/Kconfig
@@ -81,9 +81,6 @@ config RWSEM_GENERIC_SPINLOCK
config RWSEM_XCHGADD_ALGORITHM
def_bool y
-config GENERIC_FIND_NEXT_BIT
- def_bool y
-
config GENERIC_HWEIGHT
def_bool y
diff --git a/arch/openrisc/Kconfig b/arch/openrisc/Kconfig
index 9ab3bf2..81b9ddb 100644
--- a/arch/openrisc/Kconfig
+++ b/arch/openrisc/Kconfig
@@ -55,9 +55,6 @@ config TRACE_IRQFLAGS_SUPPORT
config GENERIC_CSUM
def_bool y
-config GENERIC_FIND_NEXT_BIT
- def_bool y
-
source "init/Kconfig"
--
1.7.11.7
prev parent reply other threads:[~2013-03-30 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 13:34 [PATCH] " Paul Bolle
2013-03-26 2:53 ` rkuo
2013-03-28 15:04 ` Jonas Bonn
2013-03-30 9:06 ` Paul Bolle [this message]
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=1364634366.1345.111.camel@x61.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=jonas@southpole.se \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@openrisc.net \
--cc=rkuo@codeaurora.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®