From: Adrian Chadd <adrian@freebsd.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Keith Berkoben <berkoben@gmail.com>, Sujith <m.sujith@gmail.com>,
ath9k-devel <ath9k-devel@lists.ath9k.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>,
Luis.Rodriguez@atheros.com
Subject: Re: [ath9k-devel] [PATCH 0/8] ath9k_htc patches
Date: Wed, 18 May 2011 10:16:02 +0800 [thread overview]
Message-ID: <BANLkTinNmGPh6VNF28Lr8pYmCRUKbJG4Wg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=napNyMOSKT-cDR79X4ZMka9bMsg@mail.gmail.com>
On 18 May 2011 04:46, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> Patches go first into wireless-next, then stable stuff goes into
> wirless-2.6 (current RC), and then both of these get pulled into
> wireless-testing, which provides the RC fixes + the next bits, on a
> stable kernel (RC).
>
> Compat-wireless daily snapshots use linux-next so changes take a bit
> to propagate there.
>
> OpenWrt uses wireless-testing as the base tree, you can tell by
> loading the compat module, it will tell you the base tree and git tree
> tags that was used as source.
And some (eg Felix) will merge in immediate bugfixes into openwrt that
hasn't yet made it into a baked compat-wireless release.
Adrian
prev parent reply other threads:[~2011-05-18 2:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 7:10 [PATCH 0/8] ath9k_htc patches Sujith
2011-05-17 7:19 ` Luis R. Rodriguez
2011-05-17 7:21 ` Sujith
[not found] ` <BANLkTi=RvaQcTuvi+sXxNpOv6qYU_FvoEQ@mail.gmail.com>
2011-05-17 15:37 ` [ath9k-devel] " Sujith
[not found] ` <BANLkTi=8JtAEO+49sgEAAkmGVJNmZmqBog@mail.gmail.com>
2011-05-17 20:46 ` Luis R. Rodriguez
2011-05-18 2:16 ` Adrian Chadd [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=BANLkTinNmGPh6VNF28Lr8pYmCRUKbJG4Wg@mail.gmail.com \
--to=adrian@freebsd.org \
--cc=Luis.Rodriguez@atheros.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=berkoben@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=m.sujith@gmail.com \
--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).