From: Hubert Chan <hubert@uhoreg.ca>
To: reiserfs-list@namesys.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] reiserfs v3 fixes and features
Date: Wed, 14 Apr 2004 22:53:16 -0400 [thread overview]
Message-ID: <874qrmkl43.fsf@uhoreg.ca> (raw)
In-Reply-To: 1081989006.27614.110.camel@watt.suse.com
On 2.6.5, it still fails:
...
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:1752: error: structure has no member named `journal_info'
make[3]: *** [fs/reiserfs/bitmap.o] Error 1
make[2]: *** [fs/reiserfs] Error 2
make[1]: *** [fs] Error 2
(all patches applied, except for reiserfs-group-alloc-8 and
reiserfs-search_reada-5)
--
Hubert Chan <hubert@uhoreg.ca> - http://www.uhoreg.ca/
PGP/GnuPG key: 1024D/124B61FA
Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA
Key available at wwwkeys.pgp.net. Encrypted e-mail preferred.
WARNING: multiple messages have this Message-ID (diff)
From: Hubert Chan <hubert@uhoreg.ca>
To: linux-kernel@vger.kernel.org
Cc: reiserfs-list@namesys.com
Subject: Re: [PATCH] reiserfs v3 fixes and features
Date: Wed, 14 Apr 2004 22:53:16 -0400 [thread overview]
Message-ID: <874qrmkl43.fsf@uhoreg.ca> (raw)
In-Reply-To: 1081989006.27614.110.camel@watt.suse.com
On 2.6.5, it still fails:
...
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:1752: error: structure has no member named `journal_info'
make[3]: *** [fs/reiserfs/bitmap.o] Error 1
make[2]: *** [fs/reiserfs] Error 2
make[1]: *** [fs] Error 2
(all patches applied, except for reiserfs-group-alloc-8 and
reiserfs-search_reada-5)
--
Hubert Chan <hubert@uhoreg.ca> - http://www.uhoreg.ca/
PGP/GnuPG key: 1024D/124B61FA
Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA
Key available at wwwkeys.pgp.net. Encrypted e-mail preferred.
next prev parent reply other threads:[~2004-04-15 2:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 18:03 [PATCH] reiserfs v3 fixes and features Chris Mason
2004-04-06 20:14 ` Marc-Christian Petersen
2004-04-06 21:06 ` Chris Mason
2004-04-07 2:00 ` Chris Wright
2004-04-07 13:19 ` Chris Mason
2004-04-07 14:37 ` Hans Reiser
2004-04-07 13:06 ` Yury Umanets
2004-04-07 13:25 ` Chris Mason
2004-04-08 7:22 ` Yury Umanets
2004-04-09 22:02 ` Oleg Drokin
2004-04-15 0:30 ` Chris Mason
2004-04-15 2:53 ` Hubert Chan [this message]
2004-04-15 2:53 ` Hubert Chan
2004-04-15 11:37 ` Chris Mason
2004-04-15 12:12 ` Nikita Danilov
2004-04-16 15:44 ` Hubert Chan
2004-04-16 18:54 ` Chris Mason
2004-04-16 19:47 ` Marc-Christian Petersen
2004-04-16 19:59 ` Chris Mason
2004-04-16 20:06 ` Marc-Christian Petersen
2004-04-16 20:26 ` Chris Mason
2004-04-16 20:39 ` Chris Mason
2004-04-16 20:44 ` Marc-Christian Petersen
2004-04-16 20:41 ` Marc-Christian Petersen
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=874qrmkl43.fsf@uhoreg.ca \
--to=hubert@uhoreg.ca \
--cc=linux-kernel@vger.kernel.org \
--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.