linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, Johannes Berg <johannes.berg@intel.com>
Subject: Re: linux-wireless rebased (probably for the last time) on 4.4-rc1
Date: Tue, 17 Nov 2015 16:07:11 +0200	[thread overview]
Message-ID: <87oaesyb1s.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20151116195551.GD8895@tuxdriver.com> (John W. Linville's message of "Mon, 16 Nov 2015 14:55:53 -0500")

"John W. Linville" <linville@tuxdriver.com> writes:

> The wireless-testing tree has been rebased on top of 4.4-rc1.  The
> current head of the tree is eced3b090878ddba643bbed599e6edea4ad90f49.
> Please update any downstream trees accordingly!
>
> It has been almost a year since I turned-over wireless maintenance
> duties to Johannes and Kalle. At that time I agreed to continue
> maintaining the wireless-testing tree for the duration of 2015 to help
> those that were still relying on it. The end of 2015 is coming soon,
> and with it I intend to stop maintaining wireless-testing.
>
> If you are still relying on wireless-testing, then I implore you to
> find another option to satisfy your needs. If someone would like to
> continue maintaining wireless-testing yourself, then please contact
> me and I will attempt to assist you in such a transition.
>
> Thanks for all the fish!

Thank you John. I have been using wireless-testing in my main laptop for
god knows how many years and I hate to see it go. I consider it as the
safest way to test the latest wireless code as it's just the latest -rc
release from Linux plus mac80211 and wireless-drivers trees. linux-next
is just too experimental for me, I don't want that anywhere near my
laptop :) It would be interesting to know what others think about
wireless-testing and how much users that tree really has?

I hope we can find some solution and wireless-testing continues to
exist. Otherwise testing latest wireless code will become more
difficult.

-- 
Kalle Valo

  reply	other threads:[~2015-11-17 14:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-16 19:55 linux-wireless rebased (probably for the last time) on 4.4-rc1 John W. Linville
2015-11-17 14:07 ` Kalle Valo [this message]
2015-11-18 23:44   ` Bruno Antunes
2015-11-19  3:28     ` Bob Copeland

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=87oaesyb1s.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=johannes.berg@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).