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 wireless-next tree
Date: Mon, 01 Apr 2013 23:07:02 -0500 [thread overview]
Message-ID: <515A5966.7020203@lwfinger.net> (raw)
In-Reply-To: <20130402143108.129f7a97a8a05e88e53f3ff4@canb.auug.org.au>
On 04/01/2013 10:31 PM, Stephen Rothwell wrote:
> Hi Larry,
>
> On Mon, 01 Apr 2013 22:07:24 -0500 Larry Finger <Larry.Finger@lwfinger.net> wrote:
>>
>> On 04/01/2013 09:34 PM, Stephen Rothwell wrote:
>>>
>>> After merging the wireless-next tree, today's linux-next build (x86_64
>>> allmodconfig) failed like this:
>>>
>>> drivers/net/wireless/rtlwifi/rtl8188ee/dm.c:30:18: fatal error: wifi.h: No such file or directory
>>>
>>> Caused by commit f0eb856e0b6c ("rtlwifi: rtl8188ee: Add new driver").
>>> Forgot a file?
>>
>> I do not understand. File wifi.h is definitely there and is in
>> drivers/net/wireless/rtlwifi/. Use of that directory as a source of include
>> files is handled by "ccflags-y += -I drivers/net/wireless/rtlwifi
>> -D__CHECK_ENDIAN__" in the Makefile for rtl8188ee. In fact, it builds just fine
>> here.
>>
>> What am I missing?
>
> I don't know, sorry. The tree I have also has
> drivers/net/wireless/rtlwifi/wifi.h. All the other uses of wifi.h in the
> other drivers below that directory use
>
> #include "../wifi.h"
>
> Maybe it has something to do with using O=... on the command line (which I do).
I was trying to get rid of the relative directory notation, but I guess I
screwed it up somewhere. Rather than "wifi.h, I suspect I should have used <wifi.h>.
Larry
next prev parent reply other threads:[~2013-04-02 4:12 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 2:34 linux-next: build failure after merge of the wireless-next tree Stephen Rothwell
2013-04-02 3:07 ` Larry Finger
2013-04-02 3:31 ` Stephen Rothwell
2013-04-02 4:07 ` Larry Finger [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-16 2:08 Stephen Rothwell
2025-01-16 5:49 ` Ping-Ke Shih
2025-01-16 19:30 ` Kalle Valo
2024-10-09 1:04 Stephen Rothwell
2024-10-09 7:04 ` Johannes Berg
2014-09-08 8:42 Stephen Rothwell
2014-09-09 23:28 ` Stephen Rothwell
2014-09-09 23:28 ` Stephen Rothwell
2014-09-09 23:37 ` David Miller
2014-09-10 17:46 ` John W. Linville
2014-07-16 3:28 Stephen Rothwell
2014-07-16 14:09 ` John W. Linville
2014-04-23 3:47 Stephen Rothwell
2014-04-23 20:54 ` Bing Zhao
2014-03-06 2:43 Stephen Rothwell
2014-03-06 8:53 ` Arend van Spriel
2014-03-06 8:53 ` Arend van Spriel
2014-03-06 2:24 Stephen Rothwell
2014-02-25 2:35 Stephen Rothwell
2014-02-25 19:07 ` John W. Linville
2014-02-25 20:47 ` Stephen Rothwell
2014-03-04 23:16 ` Stephen Rothwell
2014-03-04 23:21 ` Stephen Rothwell
2014-03-04 23:49 ` Greg KH
2014-02-13 2:19 Stephen Rothwell
2014-02-13 2:22 ` Stephen Rothwell
2014-02-13 17:31 ` Paul Gortmaker
2014-02-13 18:22 ` Paul Gortmaker
2014-02-13 18:28 ` Greg KH
2013-07-23 1:32 Stephen Rothwell
2013-07-23 7:24 ` Hauke Mehrtens
2012-04-12 2:24 Stephen Rothwell
2012-04-12 2:24 ` Stephen Rothwell
2011-12-20 2:18 Stephen Rothwell
2011-12-20 2:42 ` Luis R. Rodriguez
2011-12-20 2:57 ` Stephen Rothwell
2011-12-20 3:24 ` Luis R. Rodriguez
2011-11-22 3:35 Stephen Rothwell
2011-11-22 8:03 ` 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=515A5966.7020203@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.