From: "John W. Linville" <linville@tuxdriver.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: Kalle Valo <kvalo@codeaurora.org>,
linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-nfc@ml01.01.org, "David S. Miller" <davem@davemloft.net>,
lwn@lwn.net
Subject: Re: changes to Linux wireless maintenance
Date: Sun, 21 Dec 2014 12:07:23 -0500 [thread overview]
Message-ID: <20141221170722.GA28648@tuxdriver.com> (raw)
In-Reply-To: <549697F0.8090506@broadcom.com>
On Sun, Dec 21, 2014 at 10:50:40AM +0100, Arend van Spriel wrote:
> >The trees work similarly like John's wireless and wireless-next trees, the
> >former only for important bugfixes to -rc releases and the latter for the
> >rest going to the next release.
>
> So are you dropping the wireless-testing tree? From earlier IRC discussion I
> figured that tree was still in demand.
I still plan to maintain a version of wireless-testing for some amount of time.
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:[~2014-12-21 17:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87388d2tbn.fsf@purkki.adurom.net>
2014-12-18 10:55 ` changes to Linux wireless maintenance Kalle Valo
2014-12-18 20:04 ` wireless-drivers patchwork status Kalle Valo
2014-12-21 9:50 ` changes to Linux wireless maintenance Arend van Spriel
2014-12-21 17:07 ` John W. Linville [this message]
2014-12-22 9:55 ` Matt Chen
2014-12-17 15:59 John W. Linville
2014-12-17 16:16 ` Marcel Holtmann
2014-12-17 16:42 ` Larry Finger
2014-12-17 16:45 ` Johannes Berg
2014-12-17 18:15 ` Rafał Miłecki
2014-12-17 19:13 ` Avinash Patil
2014-12-17 19:27 ` Nick Kossifidis
2014-12-18 15:13 ` Sedat Dilek
2014-12-18 15:30 ` Dan Williams
2014-12-18 20:03 ` Luca Coelho
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=20141221170722.GA28648@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=arend@broadcom.com \
--cc=davem@davemloft.net \
--cc=kvalo@codeaurora.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-nfc@ml01.01.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lwn@lwn.net \
/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.