[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 6 Jun 2011 23:52:29 +0800
From: Américo Wang <xiyou.wangcong@...il.com>
To: Josh Triplett <josh@...htriplett.org>
Cc: Peter Oberparleiter <oberpar@...ux.vnet.ibm.com>,
Rusty Russell <rusty@...tcorp.com.au>,
Sam Ravnborg <sam@...nborg.org>, Jeff Dike <jdike@...toit.com>,
Andi Kleen <andi@...stfloor.org>,
Huang Ying <ying.huang@...el.com>, Li Wei <W.Li@....com>,
Michael Ellerman <michaele@....ibm.com>,
Ingo Molnar <mingo@...e.hu>,
Heiko Carstens <heicars2@...ux.vnet.ibm.com>,
Martin Schwidefsky <mschwid2@...ux.vnet.ibm.com>,
Al Viro <viro@...iv.linux.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Disable CONFIG_CONSTRUCTORS when not needed by CONFIG_GCOV_KERNEL
On Sun, Jun 5, 2011 at 4:21 PM, Josh Triplett <josh@...htriplett.org> wrote:
> CONFIG_CONSTRUCTORS controls support for running constructor functions
> at kernel init time. According to commit
> b99b87f70c7785ab1e253c6220f4b0b57ce3a7f7, gcov (CONFIG_GCOV_KERNEL)
> needs this. However, CONFIG_CONSTRUCTORS currently defaults to y, with
> no option to disable it, and CONFIG_GCOV_KERNEL depends on it. Instead,
> default it to n and have CONFIG_GCOV_KERNEL select it, so that the
> normal case of CONFIG_GCOV_KERNEL=n will result in
> CONFIG_CONSTRUCTORS=n.
>
> Observed in the short list of =y values in a minimal kernel
> configuration.
>
> Signed-off-by: Josh Triplett <josh@...htriplett.org>
Yeah, this is reasonable, so,
Acked-by: WANG Cong <xiyou.wangcong@...il.com>
Thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists