From: Vince <fuzzy77@free.fr>
To: reiserfs-list@namesys.com
Cc: Chris Mason <mason@suse.com>
Subject: Re: [PATCH] updated data=ordered patch for 2.6.3
Date: Mon, 23 Feb 2004 20:35:08 +0100 [thread overview]
Message-ID: <403A55EC.1050005@free.fr> (raw)
In-Reply-To: <1077563494.23061.163.camel@watt.suse.com>
Chris Mason wrote:
> Also fixed. Patches 00* will get submitted to Andrew as soon as namesys
> reviews them.
>
> There are going into the suse kernel now too, it's time for some broader
> testing.
>
> -chris
>
>
Those patches make use of the ->journal_info field ... which is on the
other hand removed in the reiser4 kernel patch, so both patches conflict :-/
Is there any way to get both reiser4 and reiser3+data-logging in the
same kernel ? Would adding back the journal_info field be enough ?
Compilation with a reiser4-patched kernel fails with:
/usr/src/linux$ make
CHK include/linux/version.h
CC scripts/empty.o
MKELF scripts/elfconfig.h
HOSTCC scripts/file2alias.o
HOSTCC scripts/modpost.o
HOSTCC scripts/sumversion.o
HOSTLD scripts/modpost
CC arch/i386/kernel/asm-offsets.s
CHK include/asm-i386/asm_offsets.h
CHK include/linux/compile.h
CC fs/buffer.o
CC fs/reiserfs/bitmap.o
In file included from fs/reiserfs/bitmap.c:8:
include/linux/reiserfs_fs.h: In function `reiserfs_transaction_running':
include/linux/reiserfs_fs.h:1753: error: structure has no member named
`journal_info'
make[2]: *** [fs/reiserfs/bitmap.o] Error 1
make[1]: *** [fs/reiserfs] Error 2
make: *** [fs] Error 2
/usr/src/linux$ zgrep journal_info ../2004.02.06.all.diff.gz
- current->journal_info = handle;
- current->journal_info = NULL;
- current->journal_info = NULL;
- .journal_info = NULL,
- return current->journal_info;
- void *journal_info;
+ result = init_journal_info(s);
+ done_journal_info(s);
+ done_journal_info(s);
next prev parent reply other threads:[~2004-02-23 19:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 4:36 [PATCH] updated data=ordered patch for 2.6.3 Chris Mason
2004-02-23 9:42 ` Dieter Nützel
2004-02-23 19:11 ` Chris Mason
2004-02-23 19:35 ` Vince [this message]
2004-03-01 13:30 ` Christophe Saout
2004-03-01 14:01 ` Chris Mason
[not found] ` <1078151441.7036.2.camel@leto.cs.pocnet.net>
2004-03-01 14:38 ` Chris Mason
2004-03-01 15:41 ` Dieter Nützel
2004-03-02 18:14 ` Dieter Nützel
2004-03-02 18:16 ` Chris Mason
2004-03-02 18:22 ` Dieter Nützel
2004-03-02 19:53 ` Dieter Nützel
2004-03-02 20:06 ` Chris Mason
2004-03-02 21:06 ` Dieter Nützel
2004-03-02 21:48 ` Dieter Nützel
2004-03-03 2:12 ` Chris Mason
2004-03-03 9:13 ` Marc-Christian Petersen
2004-03-03 22:13 ` Dieter Nützel
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=403A55EC.1050005@free.fr \
--to=fuzzy77@free.fr \
--cc=mason@suse.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.