summaryrefslogtreecommitdiffstats
path: root/arch/sparc/Kconfig
diff options
context:
space:
mode:
authorSam Ravnborg <sam@ravnborg.org>2011-12-27 21:46:53 +0100
committerDavid S. Miller <davem@davemloft.net>2011-12-27 16:33:13 -0500
commitaea1181b0bd0a09c54546399768f359d1e198e45 (patch)
tree1cd2b545f2ea4b6d52b5e593a9da5c115598d1d6 /arch/sparc/Kconfig
parentab17da5cb9d4aaf9f04c706761d3a8024897bedd (diff)
downloadop-kernel-dev-aea1181b0bd0a09c54546399768f359d1e198e45.zip
op-kernel-dev-aea1181b0bd0a09c54546399768f359d1e198e45.tar.gz
sparc32: support atomic64_t
There is no-one that really require atomic64_t support on sparc32. But several drivers fails to build without proper atomic64 support. And for an allyesconfig build for sparc32 this is annoying. Include the generic atomic64_t support for sparc32. This has a text footprint cost: $size vmlinux (before atomic64_t support) text data bss dec hex filename 3578860 134260 108781 3821901 3a514d vmlinux $size vmlinux (after atomic64_t support) text data bss dec hex filename 3579892 130684 108781 3819357 3a475d vmlinux text increase (3579892 - 3578860) = 1032 bytes data decreases - but I fail to explain why! I have rebuild twice to check my numbers. Signed-off-by: Sam Ravnborg <sam@ravnborg.org> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'arch/sparc/Kconfig')
-rw-r--r--arch/sparc/Kconfig1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/sparc/Kconfig b/arch/sparc/Kconfig
index f92602e..27060b2 100644
--- a/arch/sparc/Kconfig
+++ b/arch/sparc/Kconfig
@@ -31,6 +31,7 @@ config SPARC
config SPARC32
def_bool !64BIT
+ select GENERIC_ATOMIC64
config SPARC64
def_bool 64BIT
OpenPOWER on IntegriCloud