All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.12: hpt34x.c:259: too few arguments to function `ide_dmaproc'
Date: Thu, 02 May 2002 20:11:23 +0200	[thread overview]
Message-ID: <3CD1814B.9000503@evision-ventures.com> (raw)
In-Reply-To: <Pine.NEB.4.44.0205022054460.21679-100000@mimas.fachschaften.tu-muenchen.de>

Uz.ytkownik Adrian Bunk napisa?:
> Just FYI:
> 
> The ide_dmaproc changes in 2.5.12 broke the compilation of hpt34x.c (I
> tried 2.5.12-dj1 but this shouldn't make a difference):
> 
> <--  snip  -->
> 
> ...
> gcc -D__KERNEL__ -I/home/bunk/linux/kernel-2.5/linux-2.5.12/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe
> -mpreferred-stack-boundary=2 -march=k6   -nostdinc -I
> /usr/lib/gcc-lib/i386-linux/2.95.4
> /include -DKBUILD_BASENAME=hpt34x  -c -o hpt34x.o hpt34x.c
> hpt34x.c: In function `config_drive_xfer_rate':
> hpt34x.c:259: too few arguments to function `ide_dmaproc'
> hpt34x.c:281: too few arguments to function `ide_dmaproc'
> hpt34x.c:304: structure has no member named `dmaproc'
> hpt34x.c:305: warning: control reaches end of non-void function
> hpt34x.c: In function `hpt34x_dmaproc':
> hpt34x.c:350: too few arguments to function `ide_dmaproc'
> hpt34x.c: In function `ide_init_hpt34x':
> hpt34x.c:426: structure has no member named `dmaproc'
> make[3]: *** [hpt34x.o] Error 1
> make[3]: Leaving directory

Just adding a trailing struct request *rq parameter
to hpt34x_dmaproc() and passing it there to ide_dmaproc
as well as changing dmaproc to udma at line 426 will do.



  reply	other threads:[~2002-05-02 19:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-02 18:57 2.5.12: hpt34x.c:259: too few arguments to function `ide_dmaproc' Adrian Bunk
2002-05-02 18:11 ` Martin Dalecki [this message]
2002-05-02 18:35 ` Martin Dalecki
2002-05-02 19:59   ` Adrian Bunk

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=3CD1814B.9000503@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --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 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.