From: Bob Copeland <me@bobcopeland.com>
To: Bruno Antunes <baantunes@gmail.com>
Cc: Kalle Valo <kvalo@codeaurora.org>,
"John W. Linville" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <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: Wed, 18 Nov 2015 22:28:50 -0500 [thread overview]
Message-ID: <20151119032850.GA29270@localhost> (raw)
In-Reply-To: <CABUTiXU-i7u=1Bbmf=RFfEJM3QYedngxnCr+vVdMPr_pFQ+-tw@mail.gmail.com>
On Wed, Nov 18, 2015 at 11:44:43PM +0000, Bruno Antunes wrote:
> On 17 November 2015 at 14:07, Kalle Valo <kvalo@codeaurora.org> wrote:
> >
> > I hope we can find some solution and wireless-testing continues to
> > exist. Otherwise testing latest wireless code will become more
> > difficult.
>
> Is this tree very difficult to maintain?
> In case there are no volunteers what will be future options for using
> the latest wireless code?
I also tend to use wireless-testing as the main kernel on my laptop, and
find it handy at times to have both recent drivers and mac80211 changes
in the same tree without resorting to backports or merging the trees
myself. Not much problem doing those, but if I'm going to do it anyway...
might as well share.
So, I'd be willing to help keep it running for a time after said sunset
date.
> says the diagram is out of date, thats obvious, since wireless tree is now
> wireless-drivers and the maintainer is Kalle.
> wireless-drivers ----> net -----> linux
> So what is the process for wireless-testing tree, the merge of linux,
> mac80211and wireless-drivers trees?
mac80211 and wireless-drivers go into net, wireless-testing doesn't
go upstream; it's exactly just for testing. That said, it's an easy
base to work against since all the bits are reasonably up-to-date.
--
Bob Copeland %% http://bobcopeland.com/
prev parent reply other threads:[~2015-11-19 3:28 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
2015-11-18 23:44 ` Bruno Antunes
2015-11-19 3:28 ` Bob Copeland [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=20151119032850.GA29270@localhost \
--to=me@bobcopeland.com \
--cc=baantunes@gmail.com \
--cc=johannes.berg@intel.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).