From: Dave Jones <davej@suse.de>
To: David Ford <david+cert@blue-labs.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.2 - reiserfs::procfs.c fails compile
Date: Tue, 15 Jan 2002 20:40:48 +0100 [thread overview]
Message-ID: <20020115204048.H32088@suse.de> (raw)
In-Reply-To: <3C448241.7000104@blue-labs.org>
In-Reply-To: <3C448241.7000104@blue-labs.org>; from david+cert@blue-labs.org on Tue, Jan 15, 2002 at 02:25:53PM -0500
On Tue, Jan 15, 2002 at 02:25:53PM -0500, David Ford wrote:
> Looks like a quick fix, ..I haven't inspected it tho.
> procfs.c:80: conversion to non-scalar type requested
> procfs.c: In function `reiserfs_super_in_proc':
> procfs.c:137: conversion to non-scalar type requested
> procfs.c: In function `reiserfs_per_level_in_proc':
> procfs.c:217: conversion to non-scalar type requested
> procfs.c: In function `reiserfs_bitmap_in_proc':
> procfs.c:296: conversion to non-scalar type requested
> procfs.c: In function `reiserfs_on_disk_super_in_proc':
> procfs.c:337: conversion to non-scalar type requested
> procfs.c: In function `reiserfs_oidmap_in_proc':
> procfs.c:390: conversion to non-scalar type requested
> procfs.c: In function `reiserfs_journal_in_proc':
> procfs.c:441: conversion to non-scalar type requested
> procfs.c:494: incompatible type for argument 1 of `bdevname'
> procfs.c: In function `reiserfs_proc_register':
> procfs.c:581: aggregate value used where an integer was expected
> make[3]: *** [procfs.o] Error 1
> make[3]: Leaving directory `/usr/local/src/linux/fs/reiserfs'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/usr/local/src/linux/fs/reiserfs'
This is fixed in -dj for a week or two now. I'll put up
a resync against 2.5.2 in a few hours after I'm happy it
passes the 'builds & boots' test on a few more boxes.
Dave.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
prev parent reply other threads:[~2002-01-15 19:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 19:25 2.5.2 - reiserfs::procfs.c fails compile David Ford
2002-01-15 19:40 ` Dave Jones [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=20020115204048.H32088@suse.de \
--to=davej@suse.de \
--cc=david+cert@blue-labs.org \
--cc=linux-kernel@vger.kernel.org \
/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.