From: Johannes Berg <johannes@sipsolutions.net>
To: Mohammed Shafi <mshajakhan@atheros.com>
Cc: Mohammed Shajakhan <Mohammed.Shajakhan@Atheros.com>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"L.Kriara@sms.ed.ac.uk" <L.Kriara@sms.ed.ac.uk>
Subject: Re: [PATCH] mac80211: Add num_stations connected in debugfs
Date: Sun, 24 Apr 2011 16:59:10 +0200 [thread overview]
Message-ID: <1303657150.3603.1.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4DB4318F.6070801@atheros.com>
On Sun, 2011-04-24 at 19:49 +0530, Mohammed Shafi wrote:
> On Sunday 24 April 2011 07:06 PM, Johannes Berg wrote:
> > On Sun, 2011-04-24 at 17:25 +0530, Mohammed Shafi Shajakhan wrote:
> >
> >> From: Mohammed Shafi Shajakhan<mshajakhan@atheros.com>
> >>
> >> this will be useful when the device is operating in AP/Ad-Hoc/Mesh
> >> mode
> >>
> > Fine with me, but this counts for all virtual interfaces.
> >
> thanks, I had not thought about that. let me also if we can separately
> have the number of stations connected to each virtual interfaces.
Probably not worth it? You can always get it with iw easily anyway, no?
Just do something like "iw wlan0 station dump | grep ... | wc -l"? :-)
johannes
next prev parent reply other threads:[~2011-04-24 14:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-24 11:55 [PATCH] mac80211: Add num_stations connected in debugfs Mohammed Shafi Shajakhan
2011-04-24 13:36 ` Johannes Berg
2011-04-24 14:19 ` Mohammed Shafi
2011-04-24 14:59 ` Johannes Berg [this message]
2011-04-24 15:27 ` Mohammed Shafi
2011-04-24 15:32 ` Johannes Berg
2011-04-25 4:30 ` Mohammed Shafi
2011-04-26 11:58 ` Lito Kriara
2011-04-26 12:03 ` Mohammed Shafi
2011-04-26 12:07 ` Johannes Berg
2011-04-26 12:10 ` Lito Kriara
2011-04-26 12:14 ` Mohammed Shafi
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=1303657150.3603.1.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=L.Kriara@sms.ed.ac.uk \
--cc=Mohammed.Shajakhan@Atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mshajakhan@atheros.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).