From: Hans Reiser <reiser@namesys.com>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: reiserfs-dev@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: [reiserfs-dev] Patch?: linux-2.5.2-pre8/fs/reiserfs kdev_t compilation fixes
Date: Sat, 05 Jan 2002 17:01:46 +0300 [thread overview]
Message-ID: <3C37074A.1020201@namesys.com> (raw)
In-Reply-To: <20020105051938.A25230@baldur.yggdrasil.com>
We'll test and release a patch on ~tuesday. Right now all programmers
are on Russian holidays.
Thanks Adam,
Hans
Adam J. Richter wrote:
> The following patch gets linux-2.5.2-pre8/fs/reiserfs to
>compile. I suspect that a lot of the conversion back and forth
>between integers and kdev_t that I have accomodated could possibly
>be eliminated by someone who understands the fs/reiserfs better.
>
> I have not tested this patch in any way. I only know that
>it compiles.
>
>
>------------------------------------------------------------------------
>
>Only in linux/fs/reiserfs: CVS
>diff -u -r linux-2.5.2-pre8/fs/reiserfs/procfs.c linux/fs/reiserfs/procfs.c
>--- linux-2.5.2-pre8/fs/reiserfs/procfs.c Fri Jan 4 19:40:37 2002
>+++ linux/fs/reiserfs/procfs.c Sat Jan 5 05:12:34 2002
>@@ -77,7 +77,7 @@
> int len = 0;
> struct super_block *sb;
>
>- sb = procinfo_prologue( ( kdev_t ) ( int ) data );
>+ sb = procinfo_prologue( to_kdev_t((int)data) );
> if( sb == NULL )
> return -ENOENT;
> len += sprintf( &buffer[ len ], "%s format\twith checks %s\n",
>@@ -134,7 +134,7 @@
> struct reiserfs_sb_info *r;
> int len = 0;
>
>- sb = procinfo_prologue( ( kdev_t ) ( int ) data );
>+ sb = procinfo_prologue( to_kdev_t((int)data) );
> if( sb == NULL )
> return -ENOENT;
> r = &sb->u.reiserfs_sb;
>@@ -214,7 +214,7 @@
> int len = 0;
> int level;
>
>- sb = procinfo_prologue( ( kdev_t ) ( int ) data );
>+ sb = procinfo_prologue( to_kdev_t((int)data) );
> if( sb == NULL )
> return -ENOENT;
> r = &sb->u.reiserfs_sb;
>@@ -293,7 +293,7 @@
> struct reiserfs_sb_info *r = &sb->u.reiserfs_sb;
> int len = 0;
>
>- sb = procinfo_prologue( ( kdev_t ) ( int ) data );
>+ sb = procinfo_prologue( to_kdev_t((int)data) );
> if( sb == NULL )
> return -ENOENT;
> r = &sb->u.reiserfs_sb;
>@@ -334,7 +334,7 @@
> int hash_code;
> int len = 0;
>
>- sb = procinfo_prologue( ( kdev_t ) ( int ) data );
>+ sb = procinfo_prologue( to_kdev_t((int)data) );
> if( sb == NULL )
> return -ENOENT;
> sb_info = &sb->u.reiserfs_sb;
>@@ -387,7 +387,7 @@
> int len = 0;
> int exact;
>
>- sb = procinfo_prologue( ( kdev_t ) ( int ) data );
>+ sb = procinfo_prologue( to_kdev_t((int)data) );
> if( sb == NULL )
> return -ENOENT;
> sb_info = &sb->u.reiserfs_sb;
>@@ -438,7 +438,7 @@
> struct reiserfs_super_block *rs;
> int len = 0;
>
>- sb = procinfo_prologue( ( kdev_t ) ( int ) data );
>+ sb = procinfo_prologue( to_kdev_t((int)data) );
> if( sb == NULL )
> return -ENOENT;
> r = &sb->u.reiserfs_sb;
>@@ -491,7 +491,7 @@
> "prepare_retry: \t%12lu\n",
>
> DJF( s_journal_block ),
>- DJF( s_journal_dev ) == 0 ? "none" : bdevname( DJF( s_journal_dev ) ),
>+ DJF( s_journal_dev ) == 0 ? "none" : bdevname( to_kdev_t( DJF( s_journal_dev ) ) ),
> DJF( s_journal_dev ),
> DJF( s_orig_journal_size ),
> DJF( s_journal_trans_max ),
>@@ -578,7 +578,7 @@
> {
> return ( sb->u.reiserfs_sb.procdir ) ? create_proc_read_entry
> ( name, 0, sb->u.reiserfs_sb.procdir, func,
>- ( void * ) ( int ) sb -> s_dev ) : NULL;
>+ ( void * ) kdev_t_to_nr( sb -> s_dev ) ) : NULL;
> }
>
> void reiserfs_proc_unregister( struct super_block *sb, const char *name )
>
prev parent reply other threads:[~2002-01-05 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-05 13:19 Patch?: linux-2.5.2-pre8/fs/reiserfs kdev_t compilation fixes Adam J. Richter
2002-01-05 14:01 ` Hans Reiser [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=3C37074A.1020201@namesys.com \
--to=reiser@namesys.com \
--cc=adam@yggdrasil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-dev@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.