From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
davem@davemloft.net
Subject: Re: [PATCH] MAINTAINERS: changes for wireless
Date: Wed, 17 Dec 2014 21:23:33 +0100 [thread overview]
Message-ID: <1418847813.2135.29.camel@sipsolutions.net> (raw)
In-Reply-To: <5491D991.30908@broadcom.com> (sfid-20141217_202931_110924_F697E311)
On Wed, 2014-12-17 at 20:29 +0100, Arend van Spriel wrote:
> > +NETWORKING DRIVERS (WIRELESS)
> > +M: Kalle Valo<kvalo@codeaurora.org>
> > +L: linux-wireless@vger.kernel.org
> > +Q: http://patchwork.kernel.org/project/linux-wireless/list/
> > +T: git git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.git/
> > +S: Maintained
> > +F: drivers/net/wireless/
>
> So what about the other paths that were in "NETWORKING [WIRELESS]".
> Couple of them are obviously maintained by Johannes, but..
The remaining ones are probably just wext, and nobody cares any more ...
I guess they're orphaned. If anyone really really really needs to have a
patch against them, and we actually end up wanting it, I'm sure we can
figure something out :)
johannes
next prev parent reply other threads:[~2014-12-17 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 17:07 [PATCH] MAINTAINERS: changes for wireless John W. Linville
2014-12-17 19:29 ` Arend van Spriel
2014-12-17 20:23 ` Johannes Berg [this message]
2014-12-18 17:42 ` David Miller
[not found] ` <20141218.124231.114306102839964827.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2014-12-18 17:58 ` John W. Linville
[not found] ` <1418836025-9035-1-git-send-email-linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2014-12-18 20:14 ` Luca Coelho
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=1418847813.2135.29.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
/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).