public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: linux-scsi@vger.kernel.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Bob Frey <bobf@advansys.com>, Jesper Juhl <jesper.juhl@gmail.com>
Subject: Build failure in advansys driver - error: implicit declaration of function 'to_pci_dev'
Date: Sun, 12 Aug 2007 01:43:16 +0200	[thread overview]
Message-ID: <200708120143.16728.jesper.juhl@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2238 bytes --]

Trying to build current Linus git tree (head at 
ac07860264bd2b18834d3fa3be47032115524cea) using the attached config 
file (generated by 'make randconfig') the build fails for me with : 

...
  CC      drivers/scsi/advansys.o
drivers/scsi/advansys.c:794:2: warning: #warning this driver is still not properly converted to the DMA API
drivers/scsi/advansys.c: In function 'advansys_board_found':
drivers/scsi/advansys.c:17781: error: implicit declaration of function 'to_pci_dev'
drivers/scsi/advansys.c:17781: warning: pointer/integer type mismatch in conditional expression
drivers/scsi/advansys.c:17788: warning: unused variable 'pci_memory_address'
drivers/scsi/advansys.c:17781: warning: unused variable 'pdev'
make[2]: *** [drivers/scsi/advansys.o] Error 1
make[1]: *** [drivers/scsi] Error 2
make: *** [drivers] Error 2

This is on a Slackware Linux 12.0 system with the following 
environment : 

$ scripts/ver_linux
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.

Linux dragon 2.6.22-g1db6178c #1 SMP PREEMPT Sat Jul 14 04:10:50 CEST 2007 i686 AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ AuthenticAMD GNU/Linux

Gnu C                  4.1.2
Gnu make               3.81
binutils               Binutils
util-linux             2.12r
mount                  2.12r
module-init-tools      3.2.2
e2fsprogs              1.39
jfsutils               1.1.11
reiserfsprogs          3.6.19
xfsprogs               2.8.16
pcmciautils            014
quota-tools            3.13.
PPP                    2.4.4
Linux C Library        2.5
Dynamic linker (ldd)   2.5
Linux C++ Library      6.0.8
Procps                 3.2.7
Net-tools              1.60
Kbd                    1.12
oprofile               0.9.2
Sh-utils               6.9
udev                   111
Modules Loaded         snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss lp snd_emu10k1 snd_rawmidi firmware_class snd_ac97_codec nvidia ac97_bus snd_pcm snd_seq_device snd_timer snd_page_alloc snd_util_mem agpgart sg snd_hwdep evdev ehci_hcd via_rhine k8temp

I've also attached a complete build log. If you need any further details, just ask.


Kind regards,
  Jesper Juhl



[-- Attachment #2: config.24.gz --]
[-- Type: application/x-gzip, Size: 7989 bytes --]

[-- Attachment #3: build.log.24.gz --]
[-- Type: application/x-gzip, Size: 6403 bytes --]

             reply	other threads:[~2007-08-11 23:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-11 23:43 Jesper Juhl [this message]
2007-08-12 11:54 ` Build failure in advansys driver - error: implicit declaration of function 'to_pci_dev' Matthew Wilcox
2007-08-12 17:00   ` Jesper Juhl

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=200708120143.16728.jesper.juhl@gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=bobf@advansys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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