From: "Tom Cranbrook" <tcranbrook@australia.edu>
To: "Mark A. Williamson" <mark.williamson@cl.cam.ac.uk>,
xen-devel@lists.sourceforge.net, tcranbrook@australia.edu
Subject: Re: Mixing patches
Date: Mon, 04 Oct 2004 13:03:55 -0400 [thread overview]
Message-ID: <416295ee.4721.0@australia.edu> (raw)
>> Are there any known problems with mixing Xen patches with any other
kernel
>> patches?
>
>Most things should apply OK. If the patch touches the i386 architecture
code
>then you'll want to run it through something like "sed 's/i386/xen/g". If
it
>touches certain parts of this code that are substantially different under
Xen
>then it might need explicit porting.
>
<groan> Well, it certainly looks like it touches arch.
Here's a patch log:
patching file kernel/exit.c
patching file kernel/fork.c
patching file kernel/sched.c
patching file mm/vmscan.c
patching file arch/i386/Kconfig
patching file arch/i386/kernel/apm.c
patching file arch/i386/kernel/cpu/common.c
patching file arch/i386/kernel/entry.S
patching file arch/i386/kernel/head.S
patching file arch/i386/kernel/process.c
patching file arch/i386/kernel/signal.c
patching file arch/i386/kernel/vm86.c
patching file arch/i386/Makefile
patching file arch/i386/mki/Makefile
patching file arch/i386/mki/mki.c
patching file arch/i386/mm/fault.c
patching file include/asm-i386/desc.h
patching file include/asm-i386/mki.h
patching file include/asm-i386/mkiversion.h
patching file include/asm-i386/segment.h
patching file include/asm-i386/thread_info.h
patching file include/linux/init_task.h
patching file include/linux/sched.h
patching file arch/i386/Makefile
patching file arch/i386/mki-adapter/get-version.c
patching file arch/i386/mki-adapter/LICENSE
patching file arch/i386/mki-adapter/Makefile
patching file arch/i386/mki-adapter/mki22.c
patching file arch/i386/mki-adapter/mki24.c
patching file arch/i386/mki-adapter/mki-adapter.h
patching file arch/i386/mki-adapter/mkifunc.h
patching file arch/i386/mki-adapter/mki-main.c
patching file arch/i386/mki-adapter/mkimki.c
patching file arch/i386/mki-adapter/mkivnet.c
patching file arch/i386/mki-adapter/README
patching file arch/i386/mki-adapter/timer.c
patching file arch/i386/mki-adapter/vneteth.h
patching file arch/i386/mki-adapter/vnetint-pub.h
This is a patch for Netraverse's Win4Lin. I am trying to figure out a way
to get an instance of Win95 running on a netsork server for several legacy
apps. I could devote a machine to it, but the Xen VM idea and migrating
server images is so compelling that I really wish I can do this in a
domain.
-------------------------------------------------------
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
next reply other threads:[~2004-10-04 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 17:03 Tom Cranbrook [this message]
2004-10-05 2:33 ` Mixing patches Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2004-10-06 18:42 Tom Cranbrook
2004-10-05 22:27 Tom Cranbrook
2004-10-06 6:32 ` Ian Pratt
2004-10-02 16:26 Tom Cranbrook
2004-10-02 17:01 ` Mark A. Williamson
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=416295ee.4721.0@australia.edu \
--to=tcranbrook@australia.edu \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=xen-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.