From: Ralf Baechle <ralf@linux-mips.org>
To: linux-mips@linux-mips.org
Subject: Oscar awards
Date: Tue, 13 Mar 2007 14:22:30 +0000 [thread overview]
Message-ID: <20070313142230.GA692@linux-mips.org> (raw)
The golden award for the most warnings in the code goes to atlas_defconfig
which build with 73 warnings. Actually not so terrible but the the SAA9730
ethernet driver is a horrible piece of code which in turn largely due to
the SAA9730 being one of most broken pieces of silicon ever marketed.
The silver medal goes to db1200_defconfig with 64 warnings and bronce
goes to sb1250-swarm_defconfig with just 48 points ;-)
So with the Viper 2 (non-)support gone all but one of the 46 MIPS defconfig
files actually build with the one exception being excite_defconfig:
CC arch/mips/basler/excite/excite_prom.o
CC arch/mips/basler/excite/excite_setup.o
arch/mips/basler/excite/excite_setup.c: In function 'excite_init_console':
arch/mips/basler/excite/excite_setup.c:115: error: 'UPIO_RM9000' undeclared (first use in this function)
arch/mips/basler/excite/excite_setup.c:115: error: (Each undeclared identifier is reported only once
arch/mips/basler/excite/excite_setup.c:115: error: for each function it appears in.)
arch/mips/basler/excite/excite_setup.c:116: error: 'PORT_RM9000' undeclared (first use in this function)
make[1]: *** [arch/mips/basler/excite/excite_setup.o] Error 1
make: *** [arch/mips/basler/excite] Error 2
make: Leaving directory `/var/tmp/kernel-orig'
Ralf
next reply other threads:[~2007-03-13 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 14:22 Ralf Baechle [this message]
2007-03-13 14:45 ` Oscar awards Thomas Koeller
2007-03-13 15:16 ` Ralf Baechle
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=20070313142230.GA692@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.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