From: Tomas Szepe <szepe@pinerecords.com>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel Mailing List <Linux-Kernel@vger.kernel.org>,
Reiserfs mail-list <Reiserfs-List@Namesys.COM>
Subject: Re: [ANNOUNCE]: reiser4
Date: Wed, 30 Oct 2002 17:22:00 +0100 [thread overview]
Message-ID: <20021030162200.GD1995@louise.pinerecords.com> (raw)
In-Reply-To: <15806.54736.737949.328809@laputa.namesys.com>
> > Nikita Danilov wrote:
> >
> > >Hello,
> > >
> > >Snapshot of reiser4 source code can be found at
> > >http://www.namesys.com/snapshots/2002.10.29/.
> > >
> > >It is set of patches against current Linus BK tree (2.5.44).
> > >
> > >
> >
> > The current Linus BK tree is quite a bit different from 2.5.44 ;-)
> >
> > Take a look at 2.5.44-bk1 at
> > ftp://ftp.kernel.org/pub/linux/kernel/v2.5/snapshots/
> >
> > A -bk2 snapshot should appear within the hour, too, with heaps of
> > additional changes.
> >
>
> Sorry, my fault.
>
> Patches in reiser4 snapshot are against Linus BK repository at
> http://linux.bkbits.net/linux-2.5. Numbers 2, 5, and 44, are, of course,
> just VERSION, PATCHLEVEL, and SUBLEVEL in the Makefile of the said
> repository.
The following is needed to compile reiser4 in 2.5.44-bk3:
diff -urN linux-2.5.44-bk3-reiser4/mm/Makefile linux-2.5.44-bk3-reiser4.1/mm/Makefile
--- linux-2.5.44-bk3-reiser4/mm/Makefile 2002-10-12 13:35:03.000000000 +0200
+++ linux-2.5.44-bk3-reiser4.1/mm/Makefile 2002-10-30 17:15:10.000000000 +0100
@@ -2,7 +2,7 @@
# Makefile for the linux memory manager.
#
-export-objs := shmem.o filemap.o mempool.o page_alloc.o page-writeback.o
+export-objs := shmem.o filemap.o mempool.o page_alloc.o page-writeback.o swap.o
obj-y := memory.o mmap.o filemap.o mprotect.o mlock.o mremap.o \
vmalloc.o slab.o bootmem.o swap.o vmscan.o page_io.o \
diff -urN linux-2.5.44-bk3-reiser4/mm/swap.c linux-2.5.44-bk3-reiser4.1/mm/swap.c
--- linux-2.5.44-bk3-reiser4/mm/swap.c 2002-10-16 10:53:13.000000000 +0200
+++ linux-2.5.44-bk3-reiser4.1/mm/swap.c 2002-10-30 17:14:23.000000000 +0100
@@ -22,6 +22,7 @@
#include <linux/mm_inline.h>
#include <linux/buffer_head.h>
#include <linux/prefetch.h>
+#include <linux/module.h>
/* How many pages do we try to swap or page in/out together? */
int page_cluster;
@@ -192,6 +193,7 @@
spin_unlock_irq(&zone->lru_lock);
__pagevec_release(pvec);
}
+EXPORT_SYMBOL(pagevec_deactivate_inactive);
/*
* Add the passed pages to the LRU, then drop the caller's refcount
next prev parent reply other threads:[~2002-10-30 16:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 17:45 [ANNOUNCE]: reiser4 Nikita Danilov
2002-10-29 18:22 ` Jeff Garzik
2002-10-29 18:39 ` Nikita Danilov
2002-10-30 16:22 ` Tomas Szepe [this message]
2002-10-30 16:29 ` Nikita Danilov
2002-10-30 2:29 ` Ross Vandegrift
2002-10-30 9:41 ` Nikita Danilov
2002-10-31 7:18 ` Hans Reiser
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=20021030162200.GD1995@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=Linux-Kernel@vger.kernel.org \
--cc=Nikita@Namesys.COM \
--cc=Reiserfs-List@Namesys.COM \
--cc=jgarzik@pobox.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 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.