Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964899Ab2JWUfi (ORCPT ); Tue, 23 Oct 2012 16:35:38 -0400 Received: from mail-qc0-f174.google.com ([209.85.216.174]:50157 "EHLO mail-qc0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964803Ab2JWUfb (ORCPT ); Tue, 23 Oct 2012 16:35:31 -0400 MIME-Version: 1.0 In-Reply-To: <1351022666-6960-158-git-send-email-keescook@chromium.org> References: <1351022666-6960-1-git-send-email-keescook@chromium.org> <1351022666-6960-158-git-send-email-keescook@chromium.org> From: Catalin Marinas Date: Tue, 23 Oct 2012 21:35:10 +0100 X-Google-Sender-Auth: 49GkG4Mjv2nOF5PYfkiEz_vu-h8 Message-ID: Subject: Re: [PATCH 157/193] lib: remove CONFIG_EXPERIMENTAL To: Kees Cook Cc: linux-kernel@vger.kernel.org, Andrew Morton , "Paul E. McKenney" , Dmitry Kasatkin , James Morris , "Darrick J. Wong" , "Michael S. Tsirkin" , Akinobu Mita , Ingo Molnar Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1324 Lines: 32 On 23 October 2012 21:03, Kees Cook wrote: > This config item has not carried much meaning for a while now and is > almost always enabled by default. As agreed during the Linux kernel > summit, remove it. > > CC: Andrew Morton > CC: "Paul E. McKenney" > CC: Dmitry Kasatkin > CC: James Morris > CC: "Darrick J. Wong" > CC: "Michael S. Tsirkin" > CC: Akinobu Mita > CC: Ingo Molnar > CC: Catalin Marinas > Signed-off-by: Kees Cook ... > config DEBUG_KMEMLEAK > bool "Kernel memory leak detector" > - depends on DEBUG_KERNEL && EXPERIMENTAL && HAVE_DEBUG_KMEMLEAK > + depends on DEBUG_KERNEL && HAVE_DEBUG_KMEMLEAK > select DEBUG_FS > select STACKTRACE if STACKTRACE_SUPPORT > select KALLSYMS For the kmemleak part: Acked-by: Catalin Marinas -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/