public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [git pull] stackprotector re-enabling patches
Date: Sat, 3 Jan 2009 14:34:55 -0800	[thread overview]
Message-ID: <20090103143455.4c23d243@infradead.org> (raw)
In-Reply-To: <20090103135513.20f14f1d@infradead.org>

On Sat, 3 Jan 2009 13:55:13 -0800
Arjan van de Ven <arjan@infradead.org> wrote:

> On Sat, 3 Jan 2009 22:43:53 +0100
> Ingo Molnar <mingo@elte.hu> wrote:
> >  
> > diff --git a/arch/x86/Kconfig.debug b/arch/x86/Kconfig.debug
> > index 10d6cc3..28f1114 100644
> > --- a/arch/x86/Kconfig.debug
> > +++ b/arch/x86/Kconfig.debug
> > @@ -117,6 +117,7 @@ config DEBUG_RODATA
> >  config DEBUG_RODATA_TEST
> >  	bool "Testcase for the DEBUG_RODATA feature"
> >  	depends on DEBUG_RODATA
> > +	default y
> >  	help
> >  	  This option enables a testcase for the DEBUG_RODATA
> >  	  feature as well as for the change_page_attr()
> 
> I think this chunk isn't meant to be there...

actually never mind.
it does make sense in general (in fact, I'd be tempted to remove the
KConfig for this one and just always do the check)


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2009-01-03 22:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-03 21:43 [git pull] stackprotector re-enabling patches Ingo Molnar
2009-01-03 21:55 ` Arjan van de Ven
2009-01-03 22:34   ` Arjan van de Ven [this message]
2009-01-03 22:44     ` Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090103143455.4c23d243@infradead.org \
    --to=arjan@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox