From: Larry Finger <Larry.Finger@lwfinger.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (wireless-next tree related)
Date: Thu, 04 Apr 2013 14:43:42 -0500 [thread overview]
Message-ID: <515DD7EE.2080903@lwfinger.net> (raw)
In-Reply-To: <20130404181043.c191e7f4aa3057e6eda151cc@canb.auug.org.au>
On 04/04/2013 02:10 AM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/net/wireless/rtlwifi/rtl8188ee/built-in.o: In function `.rtl92c_phy_ap_calibrate':
> (.text+0x21d14): multiple definition of `.rtl92c_phy_ap_calibrate'
> drivers/net/wireless/rtlwifi/rtl8192c/built-in.o:(.text+0xb1e8): first defined here
> drivers/net/wireless/rtlwifi/rtl8188ee/built-in.o: In function `rtl_hal_pwrseqcmdparsing':
> (.opd+0xed0): multiple definition of `rtl_hal_pwrseqcmdparsing'
> drivers/net/wireless/rtlwifi/rtl8723ae/built-in.o:(.opd+0x11a0): first defined here
> drivers/net/wireless/rtlwifi/rtl8188ee/built-in.o: In function `rtl92c_phy_ap_calibrate':
> (.opd+0xe58): multiple definition of `rtl92c_phy_ap_calibrate'
> drivers/net/wireless/rtlwifi/rtl8192c/built-in.o:(.opd+0x570): first defined here
> drivers/net/wireless/rtlwifi/rtl8188ee/built-in.o: In function `.rtl_hal_pwrseqcmdparsing':
> (.text+0x22164): multiple definition of `.rtl_hal_pwrseqcmdparsing'
> drivers/net/wireless/rtlwifi/rtl8723ae/built-in.o:(.text+0x297a8): first defined here
>
> Caused by commit f0eb856e0b6c ("rtlwifi: rtl8188ee: Add new driver").
>
> I reverted commit 8b138d4898a0 ("rtlwifi: rtl8188ee: Enable build of new
> driver") for today.
I don't know why it is so hard to remember to do an allyesconfig build, but I
seem to forget. The 2.5 hours it takes on my box does not help.
As you have probably seen, I just submitted a patch to fix the problem.
Thanks for the report,
Larry
next prev parent reply other threads:[~2013-04-04 19:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 7:10 linux-next: build failure after merge of the final tree (wireless-next tree related) Stephen Rothwell
2013-04-04 19:43 ` Larry Finger [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-19 6:20 Stephen Rothwell
2014-03-19 6:23 ` Grumbach, Emmanuel
2014-03-19 19:14 ` John W. Linville
2014-03-18 7:41 Stephen Rothwell
2012-06-21 5:59 Stephen Rothwell
2012-06-21 6:04 ` Arend van Spriel
2012-06-21 8:59 ` Arend van Spriel
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=515DD7EE.2080903@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sfr@canb.auug.org.au \
/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.