From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754855AbZKQLoO (ORCPT ); Tue, 17 Nov 2009 06:44:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753800AbZKQLoN (ORCPT ); Tue, 17 Nov 2009 06:44:13 -0500 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:43310 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753741AbZKQLoM (ORCPT ); Tue, 17 Nov 2009 06:44:12 -0500 Date: Tue, 17 Nov 2009 03:44:28 -0800 (PST) Message-Id: <20091117.034428.47467823.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 From: David Miller In-Reply-To: <4B028A37.1010202@gmail.com> References: <4B028A37.1010202@gmail.com> X-Mailer: Mew version 6.2.51 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: William Allen Simpson 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!