From: Ben Greear <greearb@candelatech.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Bruno Randolf <br1@einfach.org>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: wireless-testing or wireless-next
Date: Sat, 18 Sep 2010 11:51:14 -0700 [thread overview]
Message-ID: <4C950A22.6050105@candelatech.com> (raw)
In-Reply-To: <AANLkTinYo5qgXvSnQSHpLbhhBq0VG7Kh-X3dGK8NhXcj@mail.gmail.com>
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?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2010-09-18 18:51 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 [this message]
2010-09-20 14:42 ` John W. Linville
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=4C950A22.6050105@candelatech.com \
--to=greearb@candelatech.com \
--cc=br1@einfach.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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 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).