From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Alexey Dobriyan <adobriyan@gmail.com>,
James Bottomley <JBottomley@Parallels.com>
Cc: scsi <linux-scsi@vger.kernel.org>,
Linux-Next <linux-next@vger.kernel.org>
Subject: [-next] m68k proc_ops breakage
Date: Mon, 26 Mar 2012 22:06:14 +0200 [thread overview]
Message-ID: <CAMuHMdVQ9pxfRz899KVdAHhcspnhYU_H5DRCwRcsQY8cpZUqZw@mail.gmail.com> (raw)
m68k/defconfig:
In file included from drivers/scsi/atari_scsi.c:1091:
drivers/scsi/atari_NCR5380.c: In function ‘NCR5380_print_status’:
drivers/scsi/atari_NCR5380.c:736: error: implicit declaration of
function ‘NCR5380_proc_info’
drivers/scsi/atari_NCR5380.c: At top level:
drivers/scsi/atari_NCR5380.c:767: error: static declaration of
‘NCR5380_proc_info’ follows non-static declaration
drivers/scsi/atari_NCR5380.c:736: error: previous implicit declaration
of ‘NCR5380_proc_info’ was here
make[1]: *** [drivers/scsi/atari_scsi.o] Error 1
m68k/sun3_defconfig:
In file included from drivers/scsi/sun3_scsi.c:628:
drivers/scsi/sun3_NCR5380.c: In function ‘NCR5380_print_status’:
drivers/scsi/sun3_NCR5380.c:678: error: implicit declaration of
function ‘sun3scsi_proc_info’
drivers/scsi/sun3_NCR5380.c: At top level:
drivers/scsi/sun3_NCR5380.c:709: error: static declaration of
‘sun3scsi_proc_info’ follows non-static declaration
drivers/scsi/sun3_NCR5380.c:678: error: previous implicit declaration
of ‘sun3scsi_proc_info’ was here
make[1]: *** [drivers/scsi/sun3_scsi.o] Error 1
In file included from drivers/scsi/sun3_scsi_vme.c:571:
drivers/scsi/sun3_NCR5380.c: In function ‘NCR5380_print_status’:
drivers/scsi/sun3_NCR5380.c:678: error: implicit declaration of
function ‘sun3scsi_proc_info’
drivers/scsi/sun3_NCR5380.c: At top level:
drivers/scsi/sun3_NCR5380.c:709: error: static declaration of
‘sun3scsi_proc_info’ follows non-static declaration
drivers/scsi/sun3_NCR5380.c:678: error: previous implicit declaration
of ‘sun3scsi_proc_info’ was here
make[1]: *** [drivers/scsi/sun3_scsi_vme.o] Error 1
http://kisskb.ellerman.id.au/kisskb/buildresult/5967959/
http://kisskb.ellerman.id.au/kisskb/buildresult/5967969/
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2012-03-26 20:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 20:06 Geert Uytterhoeven [this message]
2012-03-27 7:22 ` [-next] m68k proc_ops breakage James Bottomley
2012-04-23 18:22 ` James Bottomley
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=CAMuHMdVQ9pxfRz899KVdAHhcspnhYU_H5DRCwRcsQY8cpZUqZw@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=JBottomley@Parallels.com \
--cc=adobriyan@gmail.com \
--cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).