From: Johannes Berg <johannes@sipsolutions.net>
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: Wed, 17 Dec 2014 17:45:51 +0100 [thread overview]
Message-ID: <1418834751.2135.26.camel@sipsolutions.net> (raw)
In-Reply-To: <20141217155951.GA3144@tuxdriver.com> (sfid-20141217_170024_328162_22665574)
> 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.
Thank you John for all the work you've put into wireless, from the
day-to-day grind of merging/bugs/etc. to organising meetings and looking
after people at conference nights (...)
Good luck with the retro-computing and whatever else you end up doing!
I guess we need to throw a party at netconf/netdev :)
johannes
next prev parent reply other threads:[~2014-12-17 16:46 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 [this message]
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
[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=1418834751.2135.26.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--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).