public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [PATCH 4/9] UML - Better diagnostics for broken configs
Date: Thu, 5 Jan 2006 19:53:41 -0500	[thread overview]
Message-ID: <20060106005341.GA12833@ccure.user-mode-linux.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0601052258350.27662@yvahk01.tjqt.qr>

On Thu, Jan 05, 2006 at 10:59:58PM +0100, Jan Engelhardt wrote:
> config MODE_TT
>         bool "Tracing thread support"
>         default y
>         help
>         This option controls whether tracing thread support is compiled
>         into UML.  Normally, this should be set to Y.  If you intend to
>         use only skas mode (and the host has the skas patch applied to it),
>         then it is OK to say N here.
> 
> Then I unfortunately do not quite understand what this is for.

The help is a bit out of date, that's all.

				Jeff

  reply	other threads:[~2006-01-06  0:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04 21:51 [PATCH 4/9] UML - Better diagnostics for broken configs Jeff Dike
2006-01-04 23:24 ` Andrew Morton
2006-01-05  2:21   ` Jeff Dike
2006-01-06 12:44     ` [2.6 patch] UML - Prevent MODE_SKAS=n and MODE_TT=n Adrian Bunk
2006-01-06 16:39       ` Jeff Dike
2006-01-06 16:18         ` Adrian Bunk
2006-01-07  5:22           ` Jeff Dike
2006-01-07  5:23       ` Jeff Dike
2006-01-05  7:45 ` [PATCH 4/9] UML - Better diagnostics for broken configs Jan Engelhardt
2006-01-05 16:14   ` Jeff Dike
2006-01-05 21:59     ` Jan Engelhardt
2006-01-06  0:53       ` Jeff Dike [this message]
2006-01-07  0:01       ` [uml-devel] " Rob Landley
2006-01-07  2:37         ` Jeff Dike
2006-01-07 15:12           ` Jan Engelhardt
2006-01-07 23:17             ` Jeff Dike
2006-01-08  3:50             ` Rob Landley

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=20060106005341.GA12833@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=akpm@osdl.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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