From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, jgarzik@pobox.com,
linux-net@vger.kernel.org, prism54-private@prism54.org,
netdev@oss.sgi.com
Subject: Re: 2.6.9-mm1: pc_debug multiple definitions
Date: Sat, 23 Oct 2004 00:07:55 +0100 [thread overview]
Message-ID: <20041023000755.E3459@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20041022133929.GA2831@stusta.de>; from bunk@stusta.de on Fri, Oct 22, 2004 at 03:39:29PM +0200
On Fri, Oct 22, 2004 at 03:39:29PM +0200, Adrian Bunk wrote:
>
> The following compile error comes from Linus' tree:
>
>
> <-- snip -->
>
> ...
> LD drivers/built-in.o
> drivers/pcmcia/built-in.o(.bss+0xf20): multiple definition of `pc_debug'
> drivers/net/built-in.o(.data+0x24ae0): first defined here
> make[1]: *** [drivers/built-in.o] Error 1
>
> <-- snip -->
>
>
> The pc_debug in drivers/pcmcia/ds.c was made non-static in Linus' tree,
> but the global definition of a global variable with such a generic name
> in drivers/net/wireless/prism54/islpci_mgt.c seems to be equally wrong.
I've forwarded it to Dominik to sort out with suggested solutions.
Hopefully Dominik will forward a fix soon.
(PS, I dropped David Hinds from the CC list - David doesn't maintain
2.6 PCMCIA.)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-10-22 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041022032039.730eb226.akpm@osdl.org>
2004-10-22 13:39 ` 2.6.9-mm1: pc_debug multiple definitions Adrian Bunk
2004-10-22 23:07 ` Russell King [this message]
2004-10-24 3:41 ` Luis R. Rodriguez
2004-10-24 9:33 ` Adrian Bunk
2004-10-24 10:05 ` Luis R. Rodriguez
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=20041023000755.E3459@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=prism54-private@prism54.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).