From: "Vladimir V. Saveliev" <vs@namesys.com>
To: David Masover <ninja@slaphack.com>
Cc: gimpel <gimpel@sonnenkinder.org>, reiserfs-list@namesys.com
Subject: Re: reiser4 on 2.6.13-rc6-realtime-preempt
Date: Sat, 13 Aug 2005 14:13:18 +0400 [thread overview]
Message-ID: <42FDC7BE.7000006@namesys.com> (raw)
In-Reply-To: <42FCF097.9090205@slaphack.com>
Hello
David Masover wrote:
> Vladimir V. Saveliev wrote:
>
>>>Hello
>
>
>>>reiser4 depends on several core kernel patches. I think you did not
>>>apply them.
>
>
> What kind of symptoms would not applying them cause?
I assumed that Gimpel did not apply core patches because he had compiling error:
fs/built-in.o(.text+0x92999): In function `reiser4_put_super': undefined reference to `rcu_barrier'.
However, the problem is that some changes are to be done to get reiser4 to work in new realtime/preempt kernels.
> I grab patches
> from -mm, but only the ones with "reiser4" in the name. They seem to
> work with minimal tweaking on my part, and no one said anything when I
> mentioned this before. They do seem solid...
>
You go right way.
>
>>>You might want to try to apply this patch
>>>ftp://ftp.namesys.com/pub/reiser4-for-2.6/2.6.12/reiser4-for-2.6.12-realtime-preempt-2.6.12-final-V0.7.51-29.patch.gz
>
>
> Should I get patches from there, instead of -mm, in the future? Which
> is more likely to be current for a given *stable* kernel,
> reiser4-for-2.6 or -mm?
reiser4-for-2.6 contains code which did not get enough stability yet.
>
prev parent reply other threads:[~2005-08-13 10:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 20:45 reiser4 on 2.6.13-rc6-realtime-preempt gimpel
2005-08-12 9:05 ` Vladimir V. Saveliev
2005-08-12 10:09 ` gimpel
2005-08-12 18:41 ` Valdis.Kletnieks
2005-08-12 18:55 ` David Masover
2005-08-12 20:40 ` gimpel
2005-08-13 10:13 ` Vladimir V. Saveliev [this message]
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=42FDC7BE.7000006@namesys.com \
--to=vs@namesys.com \
--cc=gimpel@sonnenkinder.org \
--cc=ninja@slaphack.com \
--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.