From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Cc: dennis.h.jensen@siemens.com
Subject: Re: [RFC] iw: support split wiphy dump
Date: Thu, 14 Feb 2013 16:40:22 +0100 [thread overview]
Message-ID: <1360856422.8210.2.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1360856049-2546-1-git-send-email-johannes@sipsolutions.net> (sfid-20130214_163418_636491_ECBFFDA6)
On Thu, 2013-02-14 at 16:34 +0100, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> This adds support for the new split wiphy dump,
> it only uses it for "iw list", not for "info"
> though, so far. Using it for "info" would mean
> querying the kernel capability first and then
> using get/dump (with filter) depending on that.
Dennis, are you up for implementing this in wpa_supplicant?
johannes
next prev parent reply other threads:[~2013-02-14 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 15:29 [RFC] nl80211: allow splitting wiphy information in dumps Johannes Berg
2013-02-14 15:34 ` [RFC] iw: support split wiphy dump Johannes Berg
2013-02-14 15:40 ` Johannes Berg [this message]
2013-02-15 8:56 ` Dennis H Jensen
2013-02-15 9:21 ` Johannes Berg
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=1360856422.8210.2.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dennis.h.jensen@siemens.com \
--cc=linux-wireless@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).