From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: akpm@osdl.org
Cc: jdike@addtoit.com, linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] [patch 0/17] UML updates, which must be merged before 2.6.9
Date: Tue, 12 Oct 2004 03:05:24 +0200 [thread overview]
Message-ID: <200410120305.24675.blaisorblade_spam@yahoo.it> (raw)
Andrew, sorry for sending these patches so late, but they are (mostly
one-liners) needed to fix either warnings in compilation (the patches are
safe) or probable bugs which are created by these warnings.
The Makefile patch are of another kind: actually, when I send that couple of
patches merged before -rc3, they were against my tree and absolutely
incorrect against Linus tree; sorry for not checking that; in fact UML does
not link with neither -rc3 nor -rc4 (also due to a compilation bug I already
fixed for -rc3). However, this Makefile fixes fix everything, have been
longly tested in public (hanging both in my tree, in SuSE UML tree and in
Jeff Dike's tree).
Finally, I'm sending a patch for a network corruption which is very nasty;
it's a one-liner, a resync against the copied original code and I've actually
tested it works perfectly.
So, please, even if now we are in a hurry after -rc4, merge them. It's the
only possibility for UML to actually work "out of the box".
Oh well, and sorry for sending "[uml-devel] [patch 4/6] uml: don't declare
cpu_online - fix compilation error" - I just noticed it's included in
2.6.9-rc4-mm1. All the rest applies without even any offsets to that tree,
too.
Thanks a lot for your help.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
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-12 1:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 1:05 BlaisorBlade [this message]
[not found] ` <200410130040.i9D0eA3P004443@ccure.user-mode-linux.org>
2004-10-14 22:44 ` [uml-devel] Re: [patch 0/17] UML updates, which must be merged before 2.6.9 BlaisorBlade
2004-10-18 21:16 ` Jeff Dike
2004-10-18 22:20 ` BlaisorBlade
2004-10-22 1:32 ` 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=200410120305.24675.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=akpm@osdl.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