From: Alistair John Strachan <alistair@devzero.co.uk>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ath9k working, almost
Date: Sat, 26 Jul 2008 20:55:01 +0100 [thread overview]
Message-ID: <200807262055.01388.alistair@devzero.co.uk> (raw)
In-Reply-To: <43e72e890807261236j6ae4a28fuf8eaf423cce91edf@mail.gmail.com>
On Saturday 26 July 2008 20:36:22 Luis R. Rodriguez wrote:
> On Sat, Jul 26, 2008 at 12:30 PM, Alistair John Strachan
>
> <alistair@devzero.co.uk> wrote:
> > On Saturday 26 July 2008 19:15:51 Luis R. Rodriguez wrote:
> >> On Sat, Jul 26, 2008 at 9:42 AM, Alistair John Strachan
> >>
> >> <alistair@devzero.co.uk> wrote:
> >> > Hi,
> >> >
> >> > The newly announced ath9k driver works great on an AR5418 Core 2 Duo
> >> > Macbook, WPA2-TKIP/AES et al all work fine. It would be good to see
> >> > this driver in wireless-testing, it completely replaces madwifi for
> >> > me. I used linux.git (2.6.26) + wireless-testing.git +
> >> > my-wireless-testing.git with success.
> >>
> >> Please keep in mind Linus' tree is just broken for wireless. But glad
> >> it is working for you after your tremendous strange changes on your
> >> tree...
> >
> > I explicitly said I was not using Linus' tree. Perhaps it is a
> > misunderstanding on your part. If you use git pull inside a tree that
> > another tree was originally forked from, it is much smaller and faster to
> > check out. This is the process I was describing. I am pretty sure there
> > are no "tremendous strange changes". :-)
>
> Well my concern was I believe Linus' tree has the new MQ stuff and
> wireless-testing doesn't. How did you handle that?
git pull will happily merge into a non-HEAD checkout. If you do something
like this (inside your linux-2.6 checkout):
git reset --hard v2.6.26
git pull git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git
git pull git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/my-wireless-testing.git ath9k
Then you get a minimal, incremental set of changes based on 2.6.26 (which is
what most wireless-testing users will want). There are some drawbacks but it
sure beats wasting several hundred megs on two git repos.
If you want to go back to Linus you just do:
git reset --hard v2.6.26
And it'll blow away all the merges (since you were never tracking those trees).
--
Cheers,
Alistair.
next prev parent reply other threads:[~2008-07-26 19:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 16:42 ath9k working, almost Alistair John Strachan
2008-07-26 18:15 ` Luis R. Rodriguez
2008-07-26 19:30 ` Alistair John Strachan
2008-07-26 19:36 ` Luis R. Rodriguez
2008-07-26 19:55 ` Alistair John Strachan [this message]
2008-07-27 14:59 ` Dan Williams
2008-07-27 15:07 ` Luis R. Rodriguez
2008-07-27 16:20 ` Alistair John Strachan
2008-07-27 16:30 ` Luis R. Rodriguez
2008-07-27 19:11 ` Stefanik Gábor
2008-07-27 23:11 ` Russell Senior
2008-08-04 18:30 ` Luis R. Rodriguez
2008-08-04 18:29 ` Luis R. Rodriguez
2008-08-04 18:32 ` 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=200807262055.01388.alistair@devzero.co.uk \
--to=alistair@devzero.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).