From: Arend van Spriel <arend@broadcom.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Kalle Valo <kvalo@codeaurora.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: wireless-testing repo
Date: Mon, 23 Nov 2015 12:19:06 +0100 [thread overview]
Message-ID: <5652F62A.4000109@broadcom.com> (raw)
Hi John,
We have been using the wireless-testing repo in our nightly testing and
as such appreciated the on-going support for it. I noticed your
announcement (and misplaced it) and as I prefer to keep the nightly
testing will have to do the work over here. Can you provide details on
what trees are merged into wireless-testing. Is it
wireless-drivers{,-next} and mac80211{,-next} or is there more to
consider. If other people still like this tree I can provide it through
github or so.
Regards,
Arend
next reply other threads:[~2015-11-23 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 11:19 Arend van Spriel [this message]
2015-11-23 11:31 ` wireless-testing repo Johannes Berg
2015-11-23 11:38 ` Arend van Spriel
2015-11-23 16:02 ` John W. Linville
2015-11-23 16:46 ` Bob Copeland
2015-11-25 9:22 ` Kalle Valo
2015-11-25 12:25 ` 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=5652F62A.4000109@broadcom.com \
--to=arend@broadcom.com \
--cc=kvalo@codeaurora.org \
--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).