From: Nikita Gergel <fc@yauza.ru>
To: linux-kernel@vger.kernel.org
Cc: torvalds@transmeta.com
Subject: [PATCH} 2.5.3-pre5: fs/reiserfs/procfs.c
Date: Mon, 28 Jan 2002 20:20:08 +0300 [thread overview]
Message-ID: <20020128202008.51d51485.fc@yauza.ru> (raw)
Hello!
I've found some errors while compiling 2.5.3-pre5 with CONFIG_REISERFS_PROC_INFO=y option. Seems that I've found how to fix problem with types conversations, but I'm not fully sure that I'm right.
But I've not fixed one error. It's with conversion from le32_to_cpu(rs->x) and bdevname(kdev_t). In our case we are to convert from __u32 to kdev_t, isn't it impossible? I've no idea...
----- [PATCH] -----
diff -urN linux-2.5.3-pre5/fs/reiserfs/procfs.c linux-2.5.3-pre5-patched/fs/reiserfs/procfs.c
--- linux-2.5.3-pre5/fs/reiserfs/procfs.c Wed Dec 16 23:20:00 2001
+++ linux-2.5.3-pre5-patched/fs/reiserfs/procfs.c Fri Jan 11 23:11:02 2002
@@ -30,8 +30,8 @@
*/
-static struct super_block *procinfo_prologue( kdev_t dev )
+static struct super_block *procinfo_prologue( kdev_t *dev )
{
struct super_block *result;
/* get super-block by device */
- result = get_super( dev );
+ result = get_super( *dev );
if( result != NULL ) {
@@ -78,5 +78,5 @@
struct super_block *sb;
- sb = procinfo_prologue( ( kdev_t ) ( int ) data );
+ sb = procinfo_prologue( ( kdev_t *) ( int ) data );
if( sb == NULL )
return -ENOENT;
@@ -135,5 +135,5 @@
int len = 0;
- sb = procinfo_prologue( ( kdev_t ) ( int ) data );
+ sb = procinfo_prologue( ( kdev_t *) ( int ) data );
if( sb == NULL )
return -ENOENT;
@@ -215,5 +215,5 @@
int level;
- sb = procinfo_prologue( ( kdev_t ) ( int ) data );
+ sb = procinfo_prologue( ( kdev_t *) ( int ) data );
if( sb == NULL )
return -ENOENT;
@@ -294,5 +294,5 @@
int len = 0;
- sb = procinfo_prologue( ( kdev_t ) ( int ) data );
+ sb = procinfo_prologue( ( kdev_t *) ( int ) data );
if( sb == NULL )
return -ENOENT;
@@ -337,5 +337,5 @@
int len = 0;
- sb = procinfo_prologue( ( kdev_t ) ( int ) data );
+ sb = procinfo_prologue( ( kdev_t *) ( int ) data );
if( sb == NULL )
return -ENOENT;
@@ -388,5 +388,5 @@
int exact;
- sb = procinfo_prologue( ( kdev_t ) ( int ) data );
+ sb = procinfo_prologue( ( kdev_t *) ( int ) data );
if( sb == NULL )
return -ENOENT;
@@ -439,5 +439,5 @@
int len = 0;
- sb = procinfo_prologue( ( kdev_t ) ( int ) data );
+ sb = procinfo_prologue( ( kdev_t *) ( int ) data );
if( sb == NULL )
return -ENOENT;
@@ -579,5 +579,5 @@
return ( sb->u.reiserfs_sb.procdir ) ? create_proc_read_entry
( name, 0, sb->u.reiserfs_sb.procdir, func,
- ( void * ) ( int ) sb -> s_dev ) : NULL;
+ &sb->s_dev ) : NULL;
}
----- [PATCH] -----
--
Nikita Gergel System Administrator
Moscow, Russia YAUZA-Telecom
reply other threads:[~2002-01-28 17:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020128202008.51d51485.fc@yauza.ru \
--to=fc@yauza.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®