From: Jeff Dike <jdike@addtoit.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net,
allan.graves@gmail.com
Subject: Re: [PATCH 1/10] UML - _switch_to code consolidation
Date: Thu, 15 Sep 2005 15:21:11 -0400 [thread overview]
Message-ID: <20050915192111.GD8106@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20050914223035.455f76b9.akpm@osdl.org>
On Wed, Sep 14, 2005 at 10:30:35PM -0700, Andrew Morton wrote:
> Which if any of these are -rc material? uml-return-a-real-error-code.patch?
I consider them all to be 2.6.14 material, which is why I sent them.
With the exception of uml-breakpoint-an-arbitrary-thread.patch, which
adds a bit of functionality, they are all bug fixes and code
movement/cleanup. In order of my preference of reaching mainline:
uml-remove-include-of-asm-elfh.patch
serious bug - this fixes the x86_64 build
uml-preserve-errno-in-error-paths.patch
serious bug - if you hit some of these, UML will hang
uml-return-a-real-error-code.patch
a small bug, almost a cleanup
uml-remove-a-useless-include.patch
uml-remove-an-unused-file.patch
uml-remove-some-build-warnings.patch
code cleanup
uml-move-libc-code-out-of-mem_userc-and-tempfilec.patch
uml-merge-mem_userc-and-memc.patch
code movement
uml-_switch_to-code-consolidation.patch
code cleanup - can be omitted from mainline if
uml-breakpoint-an-arbitrary-thread.patch is
uml-breakpoint-an-arbitrary-thread.patch
functionality
Jeff
next prev parent reply other threads:[~2005-09-15 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 21:55 [PATCH 1/10] UML - _switch_to code consolidation Jeff Dike
2005-09-15 5:30 ` Andrew Morton
2005-09-15 19:21 ` Jeff Dike [this message]
2005-09-15 9:58 ` Pavel Machek
2005-09-16 18:55 ` [uml-devel] " 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=20050915192111.GD8106@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=akpm@osdl.org \
--cc=allan.graves@gmail.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