All of lore.kernel.org
 help / color / mirror / Atom feed
From: mjt@nysv.org
To: Vladimir Saveliev <vs@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: mount throws a nikita-3228 on me
Date: Wed, 26 May 2004 00:11:33 +0300	[thread overview]
Message-ID: <20040525211133.GG4990@nysv.org> (raw)
In-Reply-To: <1085473856.1915.99.camel@tribesman.namesys.com>

On Tue, May 25, 2004 at 12:30:57PM +0400, Vladimir Saveliev wrote:

>> It says only small keys are supported. I think it was a Nikita-3228.[1]
>You seem to get reiser4 with an error which makes reiser4 to not compile
>properly.

Ok...

>Please try to add the below 
>#include <linux/types.h>
>#include <linux/fs.h>
>#include <asm/hardirq.h>
>#include <linux/sched.h>
>
>to reiser4.h right after line:
>#include <linux/errno.h>
>
>and remote
>/* for __u?? types */
>#include <linux/types.h>
>/* for struct super_block, etc */
>#include <linux/fs.h>
>/* for in_interrupt() */
>#include <asm/hardirq.h>
>
>#include <linux/sched.h>
>
>
>from debug.h 

Do you mean remove?

I took a new BK pull but it still has the same problem..

I will try this one more time today, but probably not report until
tomorrow morning. I need sleep ;)

BTW, just in case some other people are wondering the same as I, some
Reiser4 patch set kernels like -love5 are ported from older Namesys
code. I thought to let people know, because I thought otherwise :)

And thanks for the help, guys!

-- 
mjt


  parent reply	other threads:[~2004-05-25 21:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-25  8:00 mount throws a nikita-3228 on me mjt
2004-05-25  8:30 ` Vladimir Saveliev
2004-05-25  8:55   ` Alex Zarochentsev
2004-05-25  9:07     ` Alex Zarochentsev
2004-05-25 21:11   ` mjt [this message]
2004-05-26  5:20     ` Alex Zarochentsev
2004-05-26 20:40       ` mjt
2004-05-27  7:02         ` Vladimir Saveliev
2004-05-27  9:21           ` mjt

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=20040525211133.GG4990@nysv.org \
    --to=mjt@nysv.org \
    --cc=reiserfs-list@namesys.com \
    --cc=vs@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.