linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alessandro Suardi <alessandro.suardi@oracle.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: R.E.Wolff@BitWizard.nl, linux-kernel@vger.kernel.org
Subject: Re: drivers/atm/firestream.c doesn't compile in 2.5.33
Date: Sun, 01 Sep 2002 03:28:03 +0200	[thread overview]
Message-ID: <3D716D23.1000101@oracle.com> (raw)
In-Reply-To: Pine.NEB.4.44.0209010227250.147-100000@mimas.fachschaften.tu-muenchen.de

Adrian Bunk wrote:
> <--  snip  -->
> 
> ...
>   gcc -Wp,-MD,./.firestream.o.d -D__KERNEL__
> -I/home/bunk/linux/kernel-2.5/linux-2.5.33-full/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
> -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
> -march=k6 -nostdinc -iwithprefix include  -g  -DKBUILD_BASENAME=firestream
> -c -o firestream.o firestream.c
> firestream.c: In function `fs_open':
> firestream.c:870: called object is not a function
> firestream.c:870: parse error before string constant
> firestream.c:1097: called object is not a function
> firestream.c:1097: parse error before string constant
> firestream.c: In function `fs_close':
> firestream.c:1109: called object is not a function
> firestream.c:1109: parse error before string constant
> firestream.c:1159: called object is not a function
> firestream.c:1159: parse error before string constant

Same symptom as the cpia.c (and IrDA, too). Just change

#define func_enter() fs_dprintk (FS_DEBUG_FLOW, "fs: enter " 
__FUNCTION__ "\n")
#define func_exit()  fs_dprintk (FS_DEBUG_FLOW, "fs: exit  " 
__FUNCTION__ "\n")

to

#define func_enter() fs_dprintk (FS_DEBUG_FLOW, "fs: enter %s\n", 
__FUNCTION__)
#define func_exit()  fs_dprintk (FS_DEBUG_FLOW, "fs: exit  %s\n", 
__FUNCTION__)

(the 2.4.20-pre5 firestream.c has the fixed version already)

--alessandro

  "everything dies, baby that's a fact
    but maybe everything that dies someday comes back"
        (Bruce Springsteen, "Atlantic City")


  reply	other threads:[~2002-09-01  1:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-01  0:30 drivers/atm/firestream.c doesn't compile in 2.5.33 Adrian Bunk
2002-09-01  1:28 ` Alessandro Suardi [this message]
2002-09-01  9:14   ` Rogier Wolff
2002-09-01  9:13     ` David S. Miller

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=3D716D23.1000101@oracle.com \
    --to=alessandro.suardi@oracle.com \
    --cc=R.E.Wolff@BitWizard.nl \
    --cc=bunk@fs.tum.de \
    --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;
as well as URLs for NNTP newsgroup(s).