From 661e04df261ffe942181e05f34ff88646add0b54 Mon Sep 17 00:00:00 2001
From: Paul Mundt <lethal@linux-sh.org>
Date: Mon, 8 Sep 2008 12:10:35 +0900
Subject: [PATCH] --- yaml --- r: 116103 b: refs/heads/master c:
 fc63562ac2107dfa843f5288fe985fc6f0021c17 h: refs/heads/master i:   116101:
 018a99bc1cc147e833b0d033f8d6a58b9b344770   116099:
 2276a0a9a6c41e6b7a77c47637850e10bce26fe7   116095:
 251e67e40759aea18f55e265477c48c5558d6988 v: v3

---
 [refs]                | 2 +-
 trunk/arch/sh/Kconfig | 1 -
 2 files changed, 1 insertion(+), 2 deletions(-)

diff --git a/[refs] b/[refs]
index cab134f74753..39fb6cde6831 100644
--- a/[refs]
+++ b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: e7cb016e5a3163e2999d8715390d64eb46816655
+refs/heads/master: fc63562ac2107dfa843f5288fe985fc6f0021c17
diff --git a/trunk/arch/sh/Kconfig b/trunk/arch/sh/Kconfig
index 334917a62ecf..c5b08eb3770e 100644
--- a/trunk/arch/sh/Kconfig
+++ b/trunk/arch/sh/Kconfig
@@ -496,7 +496,6 @@ config CRASH_DUMP
 config SECCOMP
 	bool "Enable seccomp to safely compute untrusted bytecode"
 	depends on PROC_FS
-	default y
 	help
 	  This kernel feature is useful for number crunching applications
 	  that may need to compute untrusted bytecode during their