From: Dan Williams <dcbw@redhat.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-nfc@ml01.01.org, "David S. Miller" <davem@davemloft.net>,
Kalle Valo <kvalo@codeaurora.org>,
lwn@lwn.net
Subject: Re: changes to Linux wireless maintenance
Date: Thu, 18 Dec 2014 09:30:58 -0600 [thread overview]
Message-ID: <1418916658.2086.3.camel@dcbw.local> (raw)
In-Reply-To: <20141217155951.GA3144@tuxdriver.com>
On Wed, 2014-12-17 at 10:59 -0500, John W. Linville wrote:
> Greetings,
>
> Almost 9 years ago, Jeff Garzik wrote a message on LKML detailing
> the sad state of wireless LANs in the Linux world. The point of his
> message was "So... there it is. We suck. There's hope. No Luke
> Skywalker in sight.":
>
> https://lkml.org/lkml/2006/1/5/671
>
> Shortly thereafter, I became the maintainer for wireless LANs in the
> Linux kernel:
>
> https://lkml.org/lkml/2006/1/18/377
>
> Since then, we have had a number of wireless summit meetings all around
> the world. Items were discussed, patches were merged, and friendships
> were made. Over time, we garnered support from a large range of
> wireless networking vendors. Eventually even other technologies
> were sending their patches through my trees, and I was consistently
> ranked amongst the top 10 "gate keepers" for getting changes into the
> Linux kernel. In fact, a couple of years ago I even gave a talk on
> how Linux wireless got better. It has been quite a ride!
>
> https://events.linuxfoundation.org/images/stories/pdf/lfcs2012_linville.pdf
>
> Nevertheless, I think it is time for some changes. I have been
> the wireless maintainer for a long time, and I personally would
> like to develop in a different direction. Plus, I think that Linux
> will benefit from having some fresh blood involved in more of the
> maintenance duties. I will be stepping aside to let that happen.
Thanks John! It's been a great ride and you're a huge part of the
reason wireless happened. Nobody can thank you enough!
Dan
> The mac80211, bluetooth, and nfc trees have fed through me for some
> time. I am now asking these trees to send pull request directly to
> David Miller. Since these trees are managed through git, my hope is
> that they will not place any significant burden on Dave.
>
> As for the wireless driver patches, I have asked Kalle Valo
> to handle patch review and merge duties for everything under the
> drivers/net/wireless directory. This will now include not only the ath
> patches he already manages, but other drivers that don't have trees
> such as mwifiex, rt2x00, rtlwifi, and others. For consistency, the
> iwlwifi tree will also be merged through Kalle's new tree. I expect
> that Kalle will announce any relevant details in a follow-up message.
>
> The wireless-testing tree is a resource that some people value.
> I will continue to provide a wireless-testing tree. Now that tree
> will feed from the various wireless trees managed by others, probably
> with some sort of regularly scheduled pulls. Details are still to be
> determined, but the tree will still exist and will be substantially
> similar to how it has been so far.
>
> I also receive notices of new bug reports for wireless LANs on
> bugzilla.kernel.org. For now I will continue to triage those reports,
> so don't ignore me!! :-)
>
> Some may ask what I will do now -- I wish I had a specific answer.
> Immediate plans are to enjoy the coming holidays and my traditional
> year-end time away from work. After that...well, I'm sure I will
> find something to do. If you have any suggestions for good uses of
> my talents, feel free to contact me -- I'm not hard to find!
>
> In closing, I hope everyone will support Kalle and the other wireless
> maintainers at least as much as you have supported me for the past
> several years. These are good, hard working folks. You are in
> good hands!
>
> Regards,
>
> John
>
> P.S. Bonus points for anyone that finds a way for me to become a
> professional retro-computing hobbyist... :-)
next prev parent reply other threads:[~2014-12-18 15:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 15:59 changes to Linux wireless maintenance 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 [this message]
2014-12-18 20:03 ` Luca Coelho
[not found] <87388d2tbn.fsf@purkki.adurom.net>
2014-12-18 10:55 ` Kalle Valo
2014-12-21 9:50 ` Arend van Spriel
2014-12-21 17:07 ` John W. Linville
2014-12-22 9:55 ` Matt Chen
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=1418916658.2086.3.camel@dcbw.local \
--to=dcbw@redhat.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=linville@tuxdriver.com \
--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 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).