From: "John W. Linville" <linville@tuxdriver.com>
To: Ben Greear <greearb@candelatech.com>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
Bruno Randolf <br1@einfach.org>,
linux-wireless@vger.kernel.org
Subject: Re: wireless-testing or wireless-next
Date: Mon, 20 Sep 2010 10:42:39 -0400 [thread overview]
Message-ID: <20100920144238.GB2434@tuxdriver.com> (raw)
In-Reply-To: <4C950A22.6050105@candelatech.com>
On Sat, Sep 18, 2010 at 11:51:14AM -0700, Ben Greear wrote:
> On 09/16/2010 08:02 PM, Luis R. Rodriguez wrote:
> >On Thu, Sep 16, 2010 at 7:48 PM, Bruno Randolf<br1@einfach.org> wrote:
> >>John, Luis,
> >>
> >>I'm a little confused about which tree to use. I though we should base driver
> >>development on wireless-testing, but I see that you merge patches into
> >>wireless-next first. So should we re-base patches to wireless-next before we
> >>send them?
> >
> >Rule of thumb is if its large use linux-next, wireless-testing just
> >lets you actually boot a usable kernel.
>
> I saw what looked like a nice series of patches from you four days ago
> (power save, etc). But, they have not been applied to wireless-testing.
>
> Is there a tree that does contain these sorts of patches, or must
> we manually apply them to our own trees if we want to try them out?
You are just a bit unlucky in this case...
I actually did have them in wireless-testing...on my machine. :-(
I had a little merge/push hiccup that should be resolved now --
must have been in too much of a hurry for my day-off on Friday!
Sorry for the inconvenience!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2010-09-20 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 2:48 wireless-testing or wireless-next Bruno Randolf
2010-09-17 3:02 ` Luis R. Rodriguez
2010-09-18 0:19 ` John W. Linville
2010-09-18 4:01 ` Luis R. Rodriguez
2010-09-18 18:51 ` Ben Greear
2010-09-20 14:42 ` John W. Linville [this message]
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=20100920144238.GB2434@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=br1@einfach.org \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.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.