From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Bruno Randolf <br1@einfach.org>, linux-wireless@vger.kernel.org
Subject: Re: wireless-testing or wireless-next
Date: Fri, 17 Sep 2010 20:19:51 -0400 [thread overview]
Message-ID: <20100918001950.GA2178@tuxdriver.com> (raw)
In-Reply-To: <AANLkTinYo5qgXvSnQSHpLbhhBq0VG7Kh-X3dGK8NhXcj@mail.gmail.com>
On Thu, Sep 16, 2010 at 08:02:26PM -0700, 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.
Actually, I generally prefer that patches target wireless-testing.
In the even of conflicts between that and wireless-next-2.6, I can
usually sort them out myself. If not, I'll ask.
> > Also, AFAIK, compat-wireless is based on linux-next, so if I want to create a
> > compat-wireless package based on my latest driver changes (I need to do this
> > frequently for testing my driver on my platform), I always run into problems
> > because my latest driver is in wireless-testing and not in linux-next. Do you
> > have any advise on a proper workflow here?
>
> I have a "wl" branch for wireless-testing too :) the master branch is
> for linux-next.
Actually, there will almost never be anything in wireless-testing
that isn't in linux-next. linux-next pulls from wireless-next-2.6,
just as wireless-testing does.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-09-18 0:20 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 [this message]
2010-09-18 4:01 ` Luis R. Rodriguez
2010-09-18 18:51 ` Ben Greear
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=20100918001950.GA2178@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=br1@einfach.org \
--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 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).