From: Aurelien Jarno <aurelien@aurel32.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michael Buesch <mb@bu3sch.de>,
John Linville <linville@tuxdriver.com>,
Felix Fietkau <nbd@openwrt.org>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ssb: Make extif driver compilation depend on extif config
Date: Thu, 09 Aug 2007 01:13:40 +0200 [thread overview]
Message-ID: <46BA4E24.3060400@aurel32.net> (raw)
In-Reply-To: <20070808154813.abf55801.akpm@linux-foundation.org>
Andrew Morton a =E9crit :
> mips allmodconfig:
>=20
> drivers/ssb/driver_pcicore.c: In function `ssb_fixup_pcibridge':
> drivers/ssb/driver_pcicore.c:98: error: implicit declaration of funct=
ion `pcibios_enable_device'
> drivers/ssb/driver_pcicore.c: At top level:
> drivers/ssb/driver_pcicore.c:278: warning: integer overflow in expres=
sion
> drivers/ssb/driver_pcicore.c:278: warning: integer overflow in expres=
sion
Those looks like real errors.
> drivers/ssb/driver_extif.c:125: error: redefinition of 'extif_read32'
> drivers/ssb/driver_extif.c:21: error: previous definition of 'extif_r=
ead32' was here
> drivers/ssb/driver_extif.c:130: error: redefinition of 'extif_write32=
'
> drivers/ssb/driver_extif.c:26: error: previous definition of 'extif_w=
rite32' was here
> drivers/ssb/driver_extif.c:136: error: redefinition of 'serial_exists=
'
> drivers/ssb/driver_extif.c:32: error: previous definition of 'serial_=
exists' was here
> drivers/ssb/driver_extif.c:150: error: redefinition of 'ssb_extif_ser=
ial_init'
> drivers/ssb/driver_extif.c:46: error: previous definition of 'ssb_ext=
if_serial_init' was here
> drivers/ssb/driver_extif.c:181: error: redefinition of 'ssb_extif_tim=
ing_init'
> drivers/ssb/driver_extif.c:77: error: previous definition of 'ssb_ext=
if_timing_init' was here
> drivers/ssb/driver_extif.c:203: error: redefinition of 'ssb_extif_get=
_clockcontrol'
> drivers/ssb/driver_extif.c:99: error: previous definition of 'ssb_ext=
if_get_clockcontrol' was here
>=20
All the versions of driver_extif.c I have seen have at maximum around
100 lines. It looks like a patch applied twice, which make the same cod=
e
appearing twice in the .c file.
--=20
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
-
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-08-08 23:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 15:44 [PATCH] ssb: Make extif driver compilation depend on extif config Michael Buesch
2007-08-08 22:48 ` Andrew Morton
2007-08-08 23:13 ` Aurelien Jarno [this message]
2007-08-08 23:43 ` Andrew Morton
2007-08-08 23:58 ` Andrew Morton
2007-08-09 0:02 ` Michael Buesch
2007-08-09 0:10 ` Andrew Morton
2007-08-09 0:20 ` Michael Buesch
2007-08-09 0:28 ` Andrew Morton
2007-08-09 9:54 ` Michael Buesch
2007-08-09 9:44 ` Aurelien Jarno
2007-08-09 0:13 ` Andrew Morton
2007-08-09 14:01 ` John W. Linville
2007-08-09 14:38 ` Michael Buesch
2007-08-09 13:53 ` John W. Linville
2007-08-09 14:08 ` Michael Buesch
2007-08-09 14:23 ` John W. Linville
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=46BA4E24.3060400@aurel32.net \
--to=aurelien@aurel32.net \
--cc=akpm@linux-foundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=nbd@openwrt.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).