[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130402143108.129f7a97a8a05e88e53f3ff4@canb.auug.org.au>
Date: Tue, 2 Apr 2013 14:31:08 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Larry Finger <Larry.Finger@...inger.net>
Cc: "John W. Linville" <linville@...driver.com>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the wireless-next tree
Hi Larry,
On Mon, 01 Apr 2013 22:07:24 -0500 Larry Finger <Larry.Finger@...inger.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).
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists