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 warning after merge of the wireless-next tree
Date: Wed, 03 Apr 2013 20:17:01 -0500 [thread overview]
Message-ID: <515CD48D.9030607@lwfinger.net> (raw)
In-Reply-To: <20130404120402.2384c71a6e1850ebe76d62e2@canb.auug.org.au>
On 04/03/2013 08:04 PM, Stephen Rothwell wrote:
> Hi John,
>
> On Thu, 4 Apr 2013 12:00:43 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> After merging the wireless-next tree, today's linux-next build (x86_64
>> allmodconfig) produced this warning:
>>
>> x86_64-linux-gcc: warning: drivers/net/wireless/rtlwifi: linker input file unused because linking not done
>> x86_64-linux-gcc: warning: drivers/net/wireless/rtlwifi: linker input file unused because linking not done
>> x86_64-linux-gcc: warning: drivers/net/wireless/rtlwifi: linker input file unused because linking not done
>> x86_64-linux-gcc: warning: drivers/net/wireless/rtlwifi: linker input file unused because linking not done
>> x86_64-linux-gcc: warning: drivers/net/wireless/rtlwifi: linker input file unused because linking not done
>> x86_64-linux-gcc: warning: drivers/net/wireless/rtlwifi: linker input file unused because linking not done
>> x86_64-linux-gcc: warning: drivers/net/wireless/rtlwifi: linker input file unused because linking not done
>> x86_64-linux-gcc: warning: drivers/net/wireless/rtlwifi: linker input file unused because linking not done
>> x86_64-linux-gcc: warning: drivers/net/wireless/rtlwifi: linker input file unused because linking not done
>> x86_64-linux-gcc: warning: drivers/net/wireless/rtlwifi: linker input file unused because linking not done
>> x86_64-linux-gcc: warning: drivers/net/wireless/rtlwifi: linker input file unused because linking not done
>>
>> I have no idea what caused that.
>
> Though I suspect commit 8b138d4898a0 ("rtlwifi: rtl8188ee: Enable build
> of new driver") - I wonder if the gap between the "-I" and
> "drivers/net/wireless/rtlwifi" added to ccflags-y is the cause?
>
> I am using gcc 4.6.3 if that matters.
I use 4.7.2.
I'll send a patch with the space removed to see if that helps.
Larry
next prev parent reply other threads:[~2013-04-04 1:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 1:00 linux-next: build warning after merge of the wireless-next tree Stephen Rothwell
2013-04-04 1:04 ` Stephen Rothwell
2013-04-04 1:17 ` Larry Finger [this message]
2013-04-04 2:36 ` Stephen Rothwell
2013-04-04 2:58 ` Larry Finger
-- strict thread matches above, loose matches on Subject: below --
2024-02-09 3:29 Stephen Rothwell
2024-02-09 7:06 ` Johannes Berg
2023-09-14 2:49 Stephen Rothwell
2023-09-12 5:10 Stephen Rothwell
2023-03-23 3:15 Stephen Rothwell
2023-03-31 11:10 ` Kalle Valo
2023-02-15 4:20 Stephen Rothwell
2023-02-15 4:17 Stephen Rothwell
2023-01-19 5:24 Stephen Rothwell
2022-06-21 10:02 Stephen Rothwell
2022-05-17 10:00 Stephen Rothwell
2022-05-18 4:51 ` Kalle Valo
2014-09-30 8:46 Stephen Rothwell
2014-09-30 14:41 ` Larry Finger
2013-04-05 5:46 Stephen Rothwell
2011-11-22 3:25 Stephen Rothwell
2011-11-22 7:56 ` Stanislaw Gruszka
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=515CD48D.9030607@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 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).