From: Bruno Randolf <br1@einfach.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, lrodriguez@atheros.com
Subject: wireless-testing or wireless-next
Date: Fri, 17 Sep 2010 11:48:39 +0900 [thread overview]
Message-ID: <201009171148.39953.br1@einfach.org> (raw)
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?
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?
Thanks,
bruno
next reply other threads:[~2010-09-17 2:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 2:48 Bruno Randolf [this message]
2010-09-17 3:02 ` wireless-testing or wireless-next 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
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=201009171148.39953.br1@einfach.org \
--to=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).