From: mcgrof@ruslug.rutgers.edu (Luis R. Rodriguez)
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
netdev@oss.sgi.com, prism54-devel@prism54.org,
linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
David Hinds <dahinds@users.sourceforge.net>,
jgarzik@pobox.com
Subject: Re: 2.6.9-mm1: pc_debug multiple definitions
Date: Sun, 24 Oct 2004 06:05:57 -0400 [thread overview]
Message-ID: <20041024100557.GC17506@ruslug.rutgers.edu> (raw)
In-Reply-To: <20041024093340.GA4216@stusta.de>
On Sun, Oct 24, 2004 at 11:33:40AM +0200, Adrian Bunk wrote:
> On Sat, Oct 23, 2004 at 11:41:52PM -0400, Luis R. Rodriguez wrote:
> > 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.
> >
> > Great, anyone know why this change was done on ds.c ? The pc_debug on
> > prism54 comes from the original Intersil driver. It is used to for
> > debugging but we should move away from our current debugging mechanism
> > to netif_msg.
> >...
>
> pc_debug is a pretty generic name - it seems too generic in both files.
>
> In prism54, couldn't it be called prism54_pc_debug?
Sure although that's doing a half ass job. It'll fix your compile
problems for sure but ideally we should move away from the old debug
mechanisms that came with the driver originally. We do this by moving to
to netif_msg.
Luis
--
GnuPG Key fingerprint = 113F B290 C6D2 0251 4D84 A34A 6ADD 4937 E20A 525E
prev parent reply other threads:[~2004-10-24 10:05 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
2004-10-24 3:41 ` Luis R. Rodriguez
2004-10-24 9:33 ` Adrian Bunk
2004-10-24 10:05 ` Luis R. Rodriguez [this message]
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=20041024100557.GC17506@ruslug.rutgers.edu \
--to=mcgrof@ruslug.rutgers.edu \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=dahinds@users.sourceforge.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=prism54-devel@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).