rkuo
2013-03-26 02:53:37 UTC
CONFIG_GENERIC_FIND_NEXT_BIT was removed in v3.0, but reappeared in two
architectures. Remove it again.
Signed-off-by: Paul Bolle <pebolle at tiscali.nl>
---
0) Untested.
1) See commit 63e424c84429903c92a0f1e9654c31ccaf6694d0 ("arch: remove
CONFIG_GENERIC_FIND_{NEXT_BIT,BIT_LE,LAST_BIT}") for the removal of this
Kconfig symbol.
2) Sent as one patch. Feel free to tell me to split it up in two
patches.
arch/hexagon/Kconfig | 3 ---
arch/openrisc/Kconfig | 3 ---
2 files changed, 6 deletions(-)
I'd be fine pulling these into my tree to go with my next batch ofarchitectures. Remove it again.
Signed-off-by: Paul Bolle <pebolle at tiscali.nl>
---
0) Untested.
1) See commit 63e424c84429903c92a0f1e9654c31ccaf6694d0 ("arch: remove
CONFIG_GENERIC_FIND_{NEXT_BIT,BIT_LE,LAST_BIT}") for the removal of this
Kconfig symbol.
2) Sent as one patch. Feel free to tell me to split it up in two
patches.
arch/hexagon/Kconfig | 3 ---
arch/openrisc/Kconfig | 3 ---
2 files changed, 6 deletions(-)
changes, or the OpenRISC folks can if they want. Ack would be nice.
Just in case:
Acked-by: Richard Kuo <rkuo at codeaurora.org>
Thanks,
Richard Kuo
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation