From: Steven Cole <elenstev@mesatop.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] for ReiserFS 3.5.27 on 2.2.18pre23
Date: Thu, 23 Nov 2000 20:56:53 -0700 [thread overview]
Message-ID: <00112320565300.01042@localhost.localdomain> (raw)
For those of you who may want to run ReiserFS
on 2.2.18pre23 using reiserfs-3.5.27,
you may find as I did that the main reiserfs patch,
linux-2.2.17-reiserfs-3.5.27-patch, fails like this:
patching file linux/include/linux/fs.h
Hunk #1 FAILED at 279.
Hunk #2 FAILED at 393.
Hunk #3 FAILED at 516.
Hunk #4 FAILED at 560.
4 out of 4 hunks FAILED -- saving rejects to file linux/include/linux/fs.h.rej
Here is a temporary fix. The following will patch linux/include/linux/fs.h
correctly. I am currently running 2.2.18pre23 with reiserfs 3.5.27 using
this patch:
diff -u linux/include/linux/fs.h.orig linux/include/linux/fs.h
--- linux/include/linux/fs.h.orig Thu Nov 23 18:25:10 2000
+++ linux/include/linux/fs.h Thu Nov 23 18:38:15 2000
@@ -280,6 +280,7 @@
#include <linux/adfs_fs_i.h>
#include <linux/qnx4_fs_i.h>
#include <linux/usbdev_fs_i.h>
+#include <linux/reiserfs_fs_i.h>
/*
* Attribute flags. These should be or-ed together to figure out what
@@ -395,6 +396,7 @@
struct adfs_inode_info adfs_i;
struct qnx4_inode_info qnx4_i;
struct usbdev_inode_info usbdev_i;
+ struct reiserfs_inode_info reiserfs_i;
struct socket socket_i;
void *generic_ip;
} u;
@@ -520,6 +522,7 @@
#include <linux/adfs_fs_sb.h>
#include <linux/qnx4_fs_sb.h>
#include <linux/usbdev_fs_sb.h>
+#include <linux/reiserfs_fs_sb.h>
extern struct list_head super_blocks;
@@ -564,6 +567,7 @@
struct adfs_sb_info adfs_sb;
struct qnx4_sb_info qnx4_sb;
struct usbdev_sb_info usbdevfs_sb;
+ struct reiserfs_sb_info reiserfs_sb;
void *generic_sbp;
} u;
/*
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2000-11-24 4: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=00112320565300.01042@localhost.localdomain \
--to=elenstev@mesatop.com \
--cc=linux-kernel@vger.kernel.org \
/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).