linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Joseph D. Wagner" <theman@josephdwagner.info>
To: linux-c-programming@vger.kernel.org
Subject: More Pointer Woes
Date: Sun, 28 Dec 2003 19:45:30 +0600	[thread overview]
Message-ID: <200312281945.30750.theman@josephdwagner.info> (raw)

I get:

find.c:341: error: request for member `blocksize' in something not a 
structure or union

on line 341:

block_order_log.total_blocks = inode.i_blocks / ((fs->blocksize) / 512);

fs is a pointer but blocksize isn't.

This one's probably staring me in the face but I can't figure it out.  I 
need a fresh pair of eyes.

TIA guys (and gals) for all your support.

Joseph D. Wagner


             reply	other threads:[~2003-12-28 13:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-28 13:45 Joseph D. Wagner [this message]
2003-12-29  2:32 ` More Pointer Woes Jeff Woods
2003-12-28 16:06   ` Joseph D. Wagner
2003-12-29 13:44     ` Mariano Moreyra

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=200312281945.30750.theman@josephdwagner.info \
    --to=theman@josephdwagner.info \
    --cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).