From: Jeff Dike <jdike@addtoit.com>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] What to send to Andrew next
Date: Fri, 22 Oct 2004 01:16:58 -0400 [thread overview]
Message-ID: <200410220516.i9M5GwFL007932@ccure.user-mode-linux.org> (raw)
We've pretty much got -mm and -linus caught up with the updates that had been
sitting around.
At this point, my patch list is a mix of things that both are and aren't ready
for prime time. So, I'd like opinions on what's ready.
The names below are the ones at
http://user-mode-linux.sourceforge.net/patches.html
Here's my take on it:
Ready -
catch_eintr_generic_console_write
fix-some-warnings - some things left over from your patch
need-bash - I changed the comment :-)
syscall-returns - the start of the x86_64 stuff, this one cleans up
int -> long declarations in the system calls
type-sizes - ditto for some other types
syscalls - factors the system calls between generic and arch-specific
a bit better, I consider this safe because you can look at sys_call_table before
and after and see that they're the same
tmp-exec
defconfig
smp-link
fix-ptrace-interfaces - straightforward interface fixes
no-chans - makes sure something hits the screen when someone makes
a bogus config
no-timestamp
comments
Uncertain -
use-va_end - looks good to me, but have you figured out why it causes
crashes?
export-Symbols - I need to look at that phys_t change, which doesn't
belong there
Single_Linking_Step - leftovers, build linux, add archhelp, you
sent something like this to Andrew, so this may be essentially already there
do_signal and the rest of Bodo's fixes - I want his test cases before
I send these anywhere, although the ones that make UML look like the other
arches might be OK.
Dangerous -
3-level-pagetables and the rest of the x86_64 stuff
Jeff
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2004-10-22 4:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 5:16 Jeff Dike [this message]
2004-10-22 16:52 ` [uml-devel] What to send to Andrew next BlaisorBlade
2004-10-22 21:28 ` Jeff Dike
2004-10-23 3:57 ` BlaisorBlade
2004-10-25 9:05 ` Bodo Stroesser
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=200410220516.i9M5GwFL007932@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade_spam@yahoo.it \
--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