From: Johannes Berg <johannes@sipsolutions.net>
To: Sujith <m.sujith@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: Add new API for rate selection
Date: Wed, 27 Apr 2011 12:45:49 +0200 [thread overview]
Message-ID: <1303901149.3542.1.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <19895.62392.401485.495514@gargle.gargle.HOWL> (sfid-20110427_124302_999971_7FE5CCB6)
On Wed, 2011-04-27 at 16:15 +0530, Sujith wrote:
> - if (local->hw.flags & IEEE80211_HW_HAS_RATE_CONTROL)
> - return -EOPNOTSUPP;
> +static inline int drv_set_bitrate_mask(struct ieee80211_local *local,
> + struct ieee80211_sub_if_data *sdata,
> + const struct cfg80211_bitrate_mask *mask)
> +{
> + int ret = -ENOTSUPP;
I didn't even know -ENOTSUPP existed, but shouldn't it stay -EOPNOTSUPP?
johannes
next prev parent reply other threads:[~2011-04-27 10:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 10:45 [PATCH] mac80211: Add new API for rate selection Sujith
2011-04-27 10:45 ` Johannes Berg [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-26 5:24 Sujith
2011-04-26 7:10 ` 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=1303901149.3542.1.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=m.sujith@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).