From: Francesco Biscani <biscani@pd.astro.it>
To: reiserfs-list@namesys.com
Subject: Vanilla kernel patch
Date: Thu, 7 Oct 2004 14:02:27 +0200 [thread overview]
Message-ID: <200410071402.33421.biscani@pd.astro.it> (raw)
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
Hi,
yesterday I threw together a patchset to enable reiser4 for the vanilla
2.6.9-rc3 kernel. Basically I just downloaded the broken-out -mm2 patch and
applied the reiser4 patches in the order described by the "patch-series"
file. I did this because -mm has been too unstable for me and I don't need al
the features that can be found in -cko or -klak or others patchsets.
I would like to know how many troubles I'm running into :) So far the kernel
seems to go fine and dandy, and some fsck's did not reveal any problem. I had
to manually edit the reiser4-reget-something patch, which failed because it
wanted to use the write_lock function instead of the spin_lock function that
is found in vanilla -rc3. Also, I had to apply two non-reiser4 patches. The
first added the "i_sb_list" member to the inode structure (it was the
inodes-speedup patch), the second enabled generic acl and got rid of the
"undeclared function" warning gcc gave. Now all reiser4 stuff compiles with
no warnings at all.
What are the pitfalls I'm falling in, doing this? Is this safe or is there
stuff in -mm that is absolutely needed by reiser4?
Thanks!
--
Dr. Francesco Biscani
Dipartimento di Astronomia
Università di Padova
biscani@pd.astro.it
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next reply other threads:[~2004-10-07 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 12:02 Francesco Biscani [this message]
2004-10-08 14:29 ` Vanilla kernel patch Milan Holzäpfel
2004-10-11 9:32 ` Francesco Biscani
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=200410071402.33421.biscani@pd.astro.it \
--to=biscani@pd.astro.it \
--cc=reiserfs-list@namesys.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.