linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Coelho <luca@coelho.fi>
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>,
	lwn@lwn.net, Kalle Valo <kvalo@codeaurora.org>
Subject: Re: changes to Linux wireless maintenance
Date: Thu, 18 Dec 2014 22:03:19 +0200	[thread overview]
Message-ID: <1418932999.14710.7.camel@coelho.fi> (raw)
In-Reply-To: <20141217155951.GA3144@tuxdriver.com>

Hi John,

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.

I'm coming a bit late, so I'll probably sound repetitive, but there's
just no way I could refrain from personally thanking you.  John, you've
been a great maintainer, mentor, role-model and friend for many of us in
the wireless community.  You've been a great friend personally, since
the first time we met personally, back in 2009, in Berlin.  As others
already said, you've been the hero we needed and I'm pretty sure you'll
continue being the hero you are in other communities or wherever you
will be.  Thank you so much, my friend! Hope to keep seeing you around!

--
Luca.


  parent reply	other threads:[~2014-12-18 20:03 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
2014-12-18 20:03 ` Luca Coelho [this message]
     [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=1418932999.14710.7.camel@coelho.fi \
    --to=luca@coelho.fi \
    --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).