From: Johannes Berg <johannes@sipsolutions.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] nl80211: don't document per-wiphy interface dump
Date: Thu, 29 Jan 2015 17:05:53 +0100 [thread overview]
Message-ID: <1422547553.6322.18.camel@sipsolutions.net> (raw)
In-Reply-To: <6CBE8643-DD96-45AB-9F73-4CADC7FD2277@holtmann.org>
On Thu, 2015-01-29 at 08:02 -0800, Marcel Holtmann wrote:
> > Such a feature doesn't exist and isn't really needed since you
> > probably won't have enough interfaces to make it worthwhile, so
> > just remove that from the documentation.
> we had a TODO item internally that planned to implement this actually.
I'm not sure what it buys you since you still have to deal with old
kernels and do the filtering, and there aren't that many messages
(typically you only have one NIC anyway), but hey, if you have enough
time to waste on it I guess I don't mind ... Although we should start
watching nl80211.c code size a bit more I guess :)
Can always include a revert of this in the change that actually adds it.
johannes
prev parent reply other threads:[~2015-01-29 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 15:53 [PATCH] nl80211: don't document per-wiphy interface dump Johannes Berg
2015-01-29 16:02 ` Marcel Holtmann
2015-01-29 16:05 ` Johannes Berg [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=1422547553.6322.18.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.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).