From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Triage on the pending patches
Date: Thu, 03 Mar 2005 03:22:50 -0500 [thread overview]
Message-ID: <200503030822.j238MoBY016825@ccure.user-mode-linux.org> (raw)
Since 2.6.11 is out, it's time to decide what patches go into mainline first.
Here's my cut:
Plain bug-fixes -
build
no-kexec
no-bb
slirp-is-not-ethernet
no-grep-st-ino
fix-hostfs-gid
usercopy-confusion
fix-tlb-rounding
ubd-config
failed-net-hang
long-command-line
Safe -
cleanup-userspace - rearranges code
syscall-speedup - removes code
syscall-debug - makes some code configurable
pread - adds a comment
remove-useless-code - removes a no-op wrapper
user-obj-cleanup - build cleanup
x86_64-ldt - eliminates a reference to mm_indirect
x86-64-warning - changes some errors from panics to printks
error-reporting - prints out warnings where there weren't any before
static-tty-chan - makes a bunch of things static
stack-expansion - makes UML behave like the underlying arch
no-mo-perl - generate config.c with sed
That's 23 of the 78. We also need to resurrect the SA_NODEFER patch.
The skas0 stuff needs more baking. The os-dependent code movement I'm going
to sit on until we have it all in hand and can clean it up.
After that, some of the cleanups like the ubd-mmap removal and tlb flush
cleaning can go.
winch-crash will be nice to get in once we have agreement that it's correct.
no-sys-ptrace seems OK, but it's large, which makes me nervous. Maybe that's
a reason to get it in early.
fp-state is probably another good early candidate, as is no-bb.
user-constants-dep seems OK, but I just dropped in without understanding it.
random is OK, but needs a bit more work, in particular, it needs to be
configurable.
Jeff
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
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:[~2005-03-03 5:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 8:22 Jeff Dike [this message]
2005-03-03 5:08 ` [uml-devel] Triage on the pending patches Rob Landley
2005-03-03 18:43 ` Jeff Dike
2005-03-04 2:11 ` Rob Landley
2005-03-05 15:57 ` Blaisorblade
2005-03-06 19:59 ` 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=200503030822.j238MoBY016825@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade@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