From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Rik van Riel <riel@redhat.com>
Subject: [PATCH 2.4.22-pre4] rmap15j + all BK fixes/adds
Date: Fri, 11 Jul 2003 18:48:31 +0200 [thread overview]
Message-ID: <200307111747.57211.m.c.p@wolk-project.de> (raw)
Hi all,
at the link below you can find rmap15j + all BK fixes/adds for 2.4.22-pre4.
I've done this because rmap is my favorite VM and I want to support it where
I can, and this is just a "Tons of users want to use bleeding edge -pre's so
give them a very good VM" ;)
Have fun.
P.S.: The only part I was unsure about is the s390x init.c stuff.
I've also included .22-BK mainline cset 1.1086 which is a showstopper.
I've not attached the patch to this mail because it's kinda large.
Compiles, boots, works [tm] on my x86 machine :)
- Linux codeman 2.4.22-pre4-rmap15j #1 Fri Jul 11 18:16:38 CEST 2003 i686
- gcc version 3.3.1 20030626 (Debian prerelease)
URL:
----
http://wolk.sf.net/tmp/linux-2.4.22-pre4-rmap15j+bkfixes.patch
md5sum:
-------
0c39e54f1b3af8f076fdbe7669439e40
ciao, Marc
reply other threads:[~2003-07-11 16:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200307111747.57211.m.c.p@wolk-project.de \
--to=m.c.p@wolk-project.de \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).