From: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: Hacking documentation updated for compat-wireless
Date: Thu, 28 Jan 2010 14:08:17 -0800 [thread overview]
Message-ID: <4B620AD1.8010908@redfish-solutions.com> (raw)
In-Reply-To: <43e72e891001281313g796316f9t4708f9fbc8853a10@mail.gmail.com>
On 01/28/2010 01:13 PM, Luis R. Rodriguez wrote:
> On Thu, Jan 28, 2010 at 11:27 AM, Philip A. Prindeville
> <philipp_subx@redfish-solutions.com> wrote:
>> On 01/22/2010 01:18 PM, Luis R. Rodriguez wrote:
>>> I've updated the hacking documentation for compat-wireless, please let
>>> me know if there are any questions:
>>>
>>> http://wireless.kernel.org/en/users/Download/hacking
>>>
>>> Luis
>>
>> Hi Luis,
>>
>> Finally got around to reading this. A couple of things weren't clear to me.
>>
>> On the page, if the $HOME is assumed to be /home/user, then:
>>
>> $HOME/wireless-testing is where the generated snapshot is left;
>>
>> the "git clone" of linux-next, compat, and compat-wireless-2.6 all happen directly in $HOME;
>>
>> Running this, however, doesn't work:
>>
>> [philipp@builder ~/cw]$ env | grep GIT
>> GIT_TREE=/home/philipp/cw/wireless-testing
>
> GIT_TREE should be your linux-next tree not wireless-testing tree.
>
> Luis
Ok, you might want to correct the Wiki then.
Also, in a cross-building environment, I'm not sure why admin-clean.sh mucks with the host's kernel sources:
$ scripts/admin-clean.sh
cat: /home/philipp/cw/compat-wireless-2.6/compat-release: No such file or directory
cat: /home/philipp/cw/compat-wireless-2.6/compat-release: No such file or directory
make[1]: Entering directory `/usr/src/kernels/2.6.32.4-30.fc12.x86_64'
scripts/Makefile.clean:17: /home/philipp/cw/compat-wireless-2.6/drivers/bluetooth/Makefile: No such file or directory
make[3]: *** No rule to make target `/home/philipp/cw/compat-wireless-2.6/drivers/bluetooth/Makefile'. Stop.
make[2]: *** [/home/philipp/cw/compat-wireless-2.6/drivers/bluetooth] Error 2
make[1]: *** [_clean_/home/philipp/cw/compat-wireless-2.6] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.32.4-30.fc12.x86_64'
make: *** [clean] Error 2
Cleaned wireless-bt-compat-2.6
$
next prev parent reply other threads:[~2010-01-28 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 21:18 Hacking documentation updated for compat-wireless Luis R. Rodriguez
2010-01-28 19:27 ` Philip A. Prindeville
2010-01-28 21:13 ` Luis R. Rodriguez
2010-01-28 22:08 ` Philip A. Prindeville [this message]
2010-01-28 22:16 ` Luis R. Rodriguez
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=4B620AD1.8010908@redfish-solutions.com \
--to=philipp_subx@redfish-solutions.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.