From: Jeff Dike <jdike@addtoit.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: user-mode-linux-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: RFC: UML: remove MODE_TT?
Date: Tue, 12 Dec 2006 23:18:37 -0500 [thread overview]
Message-ID: <20061213041837.GA8825@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20061212233533.GB28443@stusta.de>
On Wed, Dec 13, 2006 at 12:35:33AM +0100, Adrian Bunk wrote:
> MODE_TT is both marked as deprecated and marked as BROKEN.
>
> Would a patch to remove MODE_TT, always enable MODE_SKAS, and doing all
> possible cleanups after this be accepted?
Thanks, but not yet.
I've got that queued up in my tree now, waiting for SMP to work. SMP is
the one remaining justification for TT mode, so I'll get that in, then remove
MODE_TT and do the associated cleanups.
Jeff
--
Work email - jdike at linux dot intel dot com
next prev parent reply other threads:[~2006-12-13 5:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 23:35 RFC: UML: remove MODE_TT? Adrian Bunk
2006-12-13 4:18 ` Jeff Dike [this message]
2007-07-28 15:47 ` Adrian Bunk
2007-08-03 17:31 ` Jeff Dike
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=20061213041837.GA8825@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=bunk@stusta.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