From: Michael Buesch <mb@bu3sch.de>
To: David Miller <davem@davemloft.net>
Cc: joe@perches.com, netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: net-2.6.24 - build failure
Date: Fri, 21 Sep 2007 18:18:04 +0200 [thread overview]
Message-ID: <200709211818.05232.mb@bu3sch.de> (raw)
In-Reply-To: <20070919.151712.66176476.davem@davemloft.net>
On Thursday 20 September 2007 00:17:12 David Miller wrote:
> From: Joe Perches <joe@perches.com>
> Date: Wed, 19 Sep 2007 14:53:22 -0700
>
> > drivers/net/wireless/b43legacy/built-in.o: In function `tsf_read_file':
> > drivers/net/wireless/b43legacy/debugfs.c:80: multiple definition of `tsf_read_file'
>
> Can one of the wireless folks fix b43legacy to not use the same
> global variable and function names as the b43 driver?
Fixes are already submitted.
This was only an accident (forgot static).
--
Greetings Michael.
prev parent reply other threads:[~2007-09-21 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 21:53 net-2.6.24 - build failure Joe Perches
2007-09-19 22:17 ` David Miller
2007-09-20 0:11 ` Larry Finger
2007-09-20 0:11 ` Larry Finger
2007-09-20 0:18 ` David Miller
2007-09-21 16:18 ` Michael Buesch [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=200709211818.05232.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.