linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC 1/2] nl80211: support per-rate/per-station statistics
Date: Fri, 16 Jan 2015 11:50:32 +0100	[thread overview]
Message-ID: <1421405432.9214.2.camel@sipsolutions.net> (raw)
In-Reply-To: <874mrrvw3z.fsf@nemi.mork.no>

On Fri, 2015-01-16 at 11:49 +0100, Bjørn Mork wrote:
> Johannes Berg <johannes@sipsolutions.net> writes:
> 
> > +void cfg80211_report_rate_stats(struct wiphy *wiphy, struct wireless_dev *wdev,
> > +				const u8 *addr, unsigned int n_stats,
> > +				struct cfg80211_rate_stats *stats, gfp_t gfp);
> > +
> >  /* ethtool helper */
> >  void cfg80211_get_drvinfo(struct net_device *dev, struct ethtool_drvinfo *info);
> >  
> > diff --git a/include/uapi/linux/nl80211.h b/include/uapi/linux/nl80211.h
> > index f52797a90816..d03e3caef505 100644
> > --- a/include/uapi/linux/nl80211.h
> > +++ b/include/uapi/linux/nl80211.h
> > @@ -35,6 +35,7 @@
> >  #define NL80211_MULTICAST_GROUP_MLME		"mlme"
> >  #define NL80211_MULTICAST_GROUP_VENDOR		"vendor"
> >  #define NL80211_MULTICAST_GROUP_TESTMODE	"testmode"
> > +#define NL80211_MULTICAST_GROUP_RATESTATS	"rate-stats"
> >  
> >  /**
> >   * DOC: Station handling
> > @@ -796,6 +797,10 @@
> >   *	as an event to indicate changes for devices with wiphy-specific regdom
> >   *	management.
> >   *
> > + * @NL80211_CMD_GET_RATE_STATISTICS: This command can be used to trigger the
> 
> So in a few lines we have all these phrases describing the same feature
> in different contexts (3 of which are different even after ignoring
> casing and _/- translation):
> 
>  rate_stats
>  RATESTATS
>  rate-stats
>  RATE_STATISTICS
> 
> How about sticking to one phrase to avoid having to look these up every
> time you use them? 

Heh, that's a good point. "ratestats" is good with me - I guess that's
pretty much a consequence of working on the code for such a long
time :-)

johannes


      reply	other threads:[~2015-01-16 10:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16  9:48 [RFC 1/2] nl80211: support per-rate/per-station statistics Johannes Berg
2015-01-16  9:48 ` [RFC 2/2] mac80211: support RX rate statistics Johannes Berg
2015-01-17  1:54   ` Sujith Manoharan
2015-01-19  9:55     ` Johannes Berg
2015-01-20  4:50       ` Sujith Manoharan
2015-01-20 11:06         ` Johannes Berg
2015-01-16 10:49 ` [RFC 1/2] nl80211: support per-rate/per-station statistics Bjørn Mork
2015-01-16 10:50   ` 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=1421405432.9214.2.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=bjorn@mork.no \
    --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).