[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100904021627.GA7695@suse.de>
Date: Fri, 3 Sep 2010 19:16:27 -0700
From: Greg KH <gregkh@...e.de>
To: Vipin Mehta <Vipin.Mehta@...eros.com>
Cc: Randy Dunlap <randy.dunlap@...cle.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for September 3 (ar6k)
On Fri, Sep 03, 2010 at 07:02:36PM -0700, Vipin Mehta wrote:
> Apologies for the inconvenience. I synced to the linux-next tree and looked into the drivers/staging/ath6kl directory. I was able to compile the driver without any issues.
>
> One of the reasons this might happen is if the following symbolic link is broken.
>
> drivers/staging/ath6kl/include/common/AR6002/hw2.0/hw
>
> The link should point to drivers/staging/ath6kl/include/common/AR6002/hw2.0/hw.0
I applied the patch and the symlink "should" be there, but in general,
we shouldn't rely on a symlink in the kernel tree to work properly.
Can you send me a patch to fix this up so it works without a symlink?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists