[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <35B17FE5076C7040809188FBE7913F983F23479B6A@SC1EXMB-MBCL.global.atheros.com>
Date: Fri, 3 Sep 2010 19:46:07 -0700
From: Vipin Mehta <Vipin.Mehta@...eros.com>
To: Greg KH <gregkh@...e.de>
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)
Sure. Will do that.
Regards,
Vipin
> -----Original Message-----
> From: Greg KH [mailto:gregkh@...e.de]
> Sent: Friday, September 03, 2010 7:16 PM
> To: Vipin Mehta
> Cc: Randy Dunlap; Stephen Rothwell; linux-next@...r.kernel.org; LKML
> 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