From: Blaisorblade <blaisorblade_spam@yahoo.it>
To: Chris Wedgwood <cw@f00f.org>
Cc: akpm@osdl.org, jdike@addtoit.com,
user-mode-linux-devel@lists.sourceforge.net,
LKML <linux-kernel@vger.kernel.org>
Subject: [uml-devel] Re: [patch 2/7] uml: Build fix for TT w/o SKAS
Date: Thu, 28 Oct 2004 23:19:47 +0200 [thread overview]
Message-ID: <200410282319.48140.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <20041028192924.GD851@taniwha.stupidest.org>
On Thursday 28 October 2004 21:29, Chris Wedgwood wrote:
> On Thu, Oct 28, 2004 at 08:49:42PM +0200, Blaisorblade wrote:
> > Drop that - the fix is in my tree currently, I'll forward it
> > soon. And the fix, instead of #ifdef'ing it out, adds the support
> > for using TT & SYSEMU.
> SKAS / SYSEMU are entirely uninteresting right now until the host OS
> support for these gets merged
Well, this is completely questionable. Even if SKAS3 will never be merged in
mainline on the host side, the SKAS3 support in UML has already been merged.
And I think SYSEMU will be much more welcome than those patches (in fact,
it's completely independent from the SKAS patch).
For an earlier discussion, see:
http://www.kerneltraffic.org/kernel-traffic/kt20030106_199.html#4
And even if SKAS3 will not be merged, SKAS4 will, and the current UML SKAS
code should need just a very few changes. While having the code in mainline
is important to get it fixed with API changes.
> i really don't think it's a good enough reason to hold other things up
> and i'd prefer to see the fixes go in as-is and further updates ontop
> of these
This would be generally right, but for now, please hold on until next -rc.
Sorry for the problem and thanks for the help!
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
This Newsletter Sponsored by: Macrovision
For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate
today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-10-28 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200410272223.i9RMNg921807@mail.osdl.org>
2004-10-28 18:49 ` [uml-devel] Re: [patch 2/7] uml: Build fix for TT w/o SKAS Blaisorblade
2004-10-28 19:29 ` Chris Wedgwood
2004-10-28 21:19 ` Blaisorblade [this message]
2004-10-28 22:20 ` roland
2004-10-28 21:50 ` roland
2004-10-28 23:45 ` Blaisorblade
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=200410282319.48140.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=akpm@osdl.org \
--cc=cw@f00f.org \
--cc=jdike@addtoit.com \
--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