public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [git pull] x86 changes for v2.6.27
Date: Tue, 15 Jul 2008 10:35:07 +0200	[thread overview]
Message-ID: <20080715083507.GB2600@elte.hu> (raw)
In-Reply-To: <alpine.LFD.1.10.0807141459440.2944@woody.linux-foundation.org>


* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Mon, 14 Jul 2008, Linus Torvalds wrote:
> > 
> > Things like this _really_ irritate me:
> > 
> > 	Memtest (MEMTEST) [Y/n/?] (NEW) ?
> 
> .. and now I get all the FTRACE stuff _individually_, with MMIOTRACE 
> (which is likely the _least_ interesting one for any normal person) 
> being turned on by default.
> 
> Ingo, you _really_ need to look at those Kconfig options. They're 
> insane.

... sorry about that - will send patches later today for all default-y 
stuff that slipped through.

default-y is handy for the development period, and i usually turn it off 
when it's close to go upstream (like i made stackprotector default-off), 
but things slip through ...

	Ingo

  reply	other threads:[~2008-07-15  8:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 13:50 [git pull] x86 changes for v2.6.27 Ingo Molnar
2008-07-14 20:49 ` Linus Torvalds
2008-07-14 20:57   ` H. Peter Anvin
2008-07-14 21:01     ` Linus Torvalds
2008-07-14 21:16       ` H. Peter Anvin
2008-07-14 21:25       ` Linus Torvalds
2008-07-14 22:00   ` Linus Torvalds
2008-07-15  8:35     ` Ingo Molnar [this message]
2008-07-15  2:51 ` Dave Jones
2008-07-15  4:33   ` Linus Torvalds
2008-07-16 13:54   ` Ingo Molnar
2008-07-16 13:52 ` Bartlomiej Zolnierkiewicz
2008-07-16 14:05   ` 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=20080715083507.GB2600@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --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