From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Exposing enum ieee80211_channel_flags to user
Date: Thu, 11 Jun 2015 15:27:16 +0200 [thread overview]
Message-ID: <1434029236.1915.13.camel@sipsolutions.net> (raw)
In-Reply-To: <55798A2C.7070300@candelatech.com>
On Thu, 2015-06-11 at 06:16 -0700, Ben Greear wrote:
> Maybe also allow the full dump with an optional --verbose flag: 'iw --verbose phy X info' ?
Well, as I said, it's not so simple to do this in the "info" handler
since you need to collect all the info first and then print it.
johannes
prev parent reply other threads:[~2015-06-11 13:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 9:35 Exposing enum ieee80211_channel_flags to user Rafał Miłecki
2015-06-11 9:45 ` Johannes Berg
2015-06-11 9:46 ` Johannes Berg
2015-06-11 10:00 ` Rafał Miłecki
2015-06-11 10:01 ` Johannes Berg
2015-06-11 13:16 ` Ben Greear
2015-06-11 13:27 ` 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=1434029236.1915.13.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.com \
/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).