From: "Matthew D. Pitts" <mpitts@suite224.net>
To: "Frank Davis" <fdavis@si.rr.com>, <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.22 : fs/intermezzo/presto.c compile error
Date: Tue, 18 Jun 2002 06:38:33 -0400 [thread overview]
Message-ID: <000b01c216b4$4c3596e0$eff583d0@pcs686> (raw)
In-Reply-To: Pine.LNX.4.44.0206180044410.3577-100000@obiwan
I have gotten this same error since about 2.5.12... I have not tried
anything earlier as yet.
Matthew
----- Original Message -----
From: "Frank Davis" <fdavis@si.rr.com>
To: <linux-kernel@vger.kernel.org>
Cc: <fdavis@si.rr.com>
Sent: Tuesday, June 18, 2002 12:49 AM
Subject: 2.5.22 : fs/intermezzo/presto.c compile error
> Hello all,
> While 'make bzImage', I received the following error
>
> presto.c: In function `presto_get_permit':
> presto.c:625: structure has no member named `p_pptr'
> presto.c: In function `presto_put_permit':
> presto.c:682: structure has no member named `p_pptr'
> presto.c: In function `presto_is_read_only':
> presto.c:1136: structure has no member named `p_pptr'
> presto.c:1139: structure has no member named `p_pptr'
> presto.c:1132: warning: `mask' might be used uninitialized in this
function
> make[2]: *** [presto.o] Error 1
> make[2]: Leaving directory `/usr/src/linux/fs/intermezzo'
> make[1]: *** [intermezzo] Error 2
> make[1]: Leaving directory `/usr/src/linux/fs'
> make: *** [fs] Error 2
>
> I think that presto_c2m(presto_cache *cache) (looked at dir.c) needs to be
> used, but I attempted that, and it didn't seem to work.
>
> Regards,
> Frank
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2002-06-18 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 4:49 2.5.22 : fs/intermezzo/presto.c compile error Frank Davis
2002-06-18 10:38 ` Matthew D. Pitts [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='000b01c216b4$4c3596e0$eff583d0@pcs686' \
--to=mpitts@suite224.net \
--cc=fdavis@si.rr.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox