From: David Miller <davem@davemloft.net>
To: william.allen.simpson@gmail.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linville@tuxdriver.com
Subject: Re: net-next-2.6 compilation errors: missing wireless/i82593.h
Date: Tue, 17 Nov 2009 03:44:28 -0800 (PST) [thread overview]
Message-ID: <20091117.034428.47467823.davem@davemloft.net> (raw)
In-Reply-To: <4B028A37.1010202@gmail.com>
From: William Allen Simpson <william.allen.simpson@gmail.com>
Date: Tue, 17 Nov 2009 06:34:15 -0500
> For the past 9-10 days, net-next-2.6 has failed to compile. In
> addition to the errors and warnings already reported here last week,
Those seemed to be for Android drivers and such, so I hope you
reported those failures to the driver maintainers as well as
linux-kernel.
For the time being could you just disable those drivers in your
build just to get work done or do you absolutely need them?
> since Nov 12th there has been another missing file. I kept hoping
> it was temporary, but no joy.
>
> /home/administer/net-next-2.6/drivers/net/znet.c:107:29: error:
> wireless/i82593.h: No such file or directory
That header file got moved out to drivers/staging along with the
wavelan driver.
The header file should instead be moved to, perhaps, include/linux
while there are still other users of it.
That's incredibly clumsy what drivers/net/znet.c is doing.
John please fix this up, thanks!
next prev parent reply other threads:[~2009-11-17 11:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 11:34 net-next-2.6 compilation errors: missing wireless/i82593.h William Allen Simpson
2009-11-17 11:44 ` David Miller [this message]
2009-11-17 11:59 ` William Allen Simpson
2009-11-17 12:13 ` Alan Cox
2009-11-17 15:20 ` [PATCH] znet: fix build failure from i82593.h relocation John W. Linville
2009-11-17 15:36 ` David Miller
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=20091117.034428.47467823.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=william.allen.simpson@gmail.com \
/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).