From: Mahesh Palivela <maheshp@posedge.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] mac80211: VHT peer STA caps
Date: Thu, 27 Sep 2012 08:53:29 +0530 [thread overview]
Message-ID: <5063C6B1.8030301@posedge.com> (raw)
In-Reply-To: <1348682036.10548.13.camel@jlt4.sipsolutions.net>
On 09/26/2012 11:23 PM, Johannes Berg wrote:
>
> Well struct ieee80211_sta is what the driver uses. That's where it's
> "telling" the driver, by making the data accessible to the driver. Your
> new vht_cap field there is also "telling the driver" that way.
>
Thanks for the pointer. will revert with code change.
>
>
> I don't think this makes sense, since we're talking only about a
> documentation change to your patch. See:
>
> * @ht_cap: HT capabilities of this STA; restricted to our own TX capabilities
> + * @vht_cap: VHT capabilities of this STA
>
> The difference is that you don't say "restricted to own", but I think
> you should explicitly say that it isn't restricted.
Oh, I got it. Thanks Johannes.
Thanks
Mahesh
next prev parent reply other threads:[~2012-09-27 3:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 3:57 [PATCH v2] mac80211: VHT peer STA caps Mahesh Palivela
2012-09-24 8:59 ` Johannes Berg
2012-09-25 5:26 ` Mahesh Palivela
2012-09-25 7:25 ` Johannes Berg
2012-09-25 9:49 ` Mahesh Palivela
2012-09-25 14:09 ` Johannes Berg
2012-09-26 3:15 ` Mahesh Palivela
2012-09-26 11:53 ` Johannes Berg
2012-09-26 17:22 ` Mahesh Palivela
2012-09-26 17:53 ` Johannes Berg
2012-09-27 3:23 ` Mahesh Palivela [this message]
2012-09-27 6:24 ` Johannes Berg
2012-09-27 6:34 ` Mahesh Palivela
2012-09-27 7:01 ` Johannes Berg
2012-09-27 7:21 ` Mahesh Palivela
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=5063C6B1.8030301@posedge.com \
--to=maheshp@posedge.com \
--cc=johannes@sipsolutions.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).