netdev - Re: net-next-2.6 compilation errors: missing wireless/i82593.h

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20091117.034428.47467823.davem@davemloft.net>
Date:	Tue, 17 Nov 2009 03:44:28 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	william.allen.simpson@...il.com
Cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	linville@...driver.com
Subject: Re: net-next-2.6 compilation errors: missing wireless/i82593.h

From: William Allen Simpson <william.allen.simpson@...il.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!
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html