From: Jason Lunz <lunz@falooley.org>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: uml-patch-2.4.23-1
Date: Sat, 20 Dec 2003 01:32:52 +0000 (UTC) [thread overview]
Message-ID: <slrnbu79m4.a5h.lunz@orr.homenet> (raw)
In-Reply-To: 20031219212840.GA8203@ccure.user-mode-linux.org
jdike@addtoit.com said:
> This patch updates UML to 2.4.23. The only change required by 2.4.23
> was the ELF_PLAT_INIT that other people saw and fixed.
um, there's also some problem if you compile the uml kernel with SMP
because of the NUM_CPUS stuff in 2.4.23.
Jason
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&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 prev parent reply other threads:[~2003-12-20 1:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 21:28 [uml-devel] uml-patch-2.4.23-1 Jeff Dike
2003-12-20 1:32 ` Jason Lunz [this message]
2003-12-21 17:41 ` Matt Ayres
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=slrnbu79m4.a5h.lunz@orr.homenet \
--to=lunz@falooley.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