From: Greg KH <gregkh@suse.de>
To: Vipin Mehta <Vipin.Mehta@Atheros.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for September 3 (ar6k)
Date: Fri, 3 Sep 2010 19:16:27 -0700 [thread overview]
Message-ID: <20100904021627.GA7695@suse.de> (raw)
In-Reply-To: <35B17FE5076C7040809188FBE7913F983F23479B57@SC1EXMB-MBCL.global.atheros.com>
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
next prev parent reply other threads:[~2010-09-04 2:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 3:52 linux-next: Tree for September 3 Stephen Rothwell
2010-09-04 1:01 ` [PATCH -next] staging: mrst touchscreen depends on SPI Randy Dunlap
2010-09-04 1:06 ` linux-next: Tree for September 3 (ar6k) Randy Dunlap
2010-09-04 2:02 ` Vipin Mehta
2010-09-04 2:16 ` Greg KH [this message]
2010-09-04 2:46 ` Vipin Mehta
2010-09-04 2:05 ` Greg KH
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=20100904021627.GA7695@suse.de \
--to=gregkh@suse.de \
--cc=Vipin.Mehta@Atheros.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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