From: Johannes Berg <johannes@sipsolutions.net>
To: Michael Wu <flamingice@sourmilk.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] cfg80211 API for channels/bitrates, mac80211 and driver conversion
Date: Fri, 04 Jan 2008 23:01:20 +0100 [thread overview]
Message-ID: <1199484080.4172.173.camel@johannes.berg> (raw)
In-Reply-To: <200712231850.37136.flamingice@sourmilk.net>
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
> > + * @power_dBm: requested transmit power
> > + * @max_antenna_gain_dBi: maximum antenna gain
> Mixed case is bad.
changed.
> > + * @IEEE80211_HW_2GHZ_SHORT_PREAMBLE_INCAPABLE:
> > + * Hardware is not capable of receiving frames with short preamble on
> > + * the 2.4 GHz band.
> Let's add it when we actually find hardware that needs it.
I disagree. It's literally two lines of code (one defining it and one
using it) and makes things more easy to discover when writing a driver.
> > + * @max_antenna_gain_dBi: maximum antenna gain in dBi
> > + * @max_power_dBm: maximum transmission power
> Again, no mixed case.
changed too
> > +extern int ieee80211_frequency_to_channel(int freqMhz);
> Mixed case again. Do you really need to add units to these names? They should
> just be all the same throughout the code.
Ok, changed.
> > + strcpy(name, "mac80211");
> >
> > return 0;
> > }
> It's simple, sure, but no. Let's not change userspace facing behavior if we
> can. If you really need to, use "IEEE 802.11".
It's pretty dumb to indicate the mode that way, but I changed it to just
"IEEE 802.11" now.
Will repost later.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2008-01-04 22:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-23 22:15 [RFC] cfg80211 API for channels/bitrates, mac80211 and driver conversion Johannes Berg
2007-12-23 23:50 ` Michael Wu
2008-01-04 22:01 ` Johannes Berg [this message]
2008-01-07 23:27 ` Luis R. Rodriguez
2008-01-08 17:17 ` Johannes Berg
2008-01-08 3:27 ` Michael Wu
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=1199484080.4172.173.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=flamingice@sourmilk.net \
--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).