From: "Arend van Spriel" <arend@broadcom.com>
To: "Mahesh Palivela" <maheshp@posedge.com>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] cfg80211/mac80211: 802.11ac changes
Date: Thu, 28 Jun 2012 14:53:50 +0200 [thread overview]
Message-ID: <4FEC53DE.70602@broadcom.com> (raw)
In-Reply-To: <952C5D5D0470AE4FB7D8A75C6ADC71CA0D612F@mbx022-e1-nj-10.exch022.domain.local>
On 06/28/2012 02:39 PM, Mahesh Palivela wrote:
> ________________________________________
> From: Johannes Berg [johannes@sipsolutions.net]
> Sent: Thursday, June 28, 2012 4:37 PM
> To: Mahesh Palivela
> Cc: linville@tuxdriver.com; linux-wireless@vger.kernel.org
> Subject: Re: [PATCH] cfg80211/mac80211: 802.11ac changes
>
>>
>> + if (sband->vht_cap.vht_supported)
>> + pos = ieee80211_ie_build_vht_cap(pos, &sband->vht_cap,
>> + sband->vht_cap.cap);
>
> indentation
>
> [MP] sorry. I didn't get. Is it sband-> line to be moved left? But previous build_ht_cap() has similar indentation
>
'sband->' should start at same column as 'pos' in the above line. Must
be tabs followed by right amount of spaces (being less than 8).
>> return pos - buffer;
>> }
>>
>> @@ -1696,6 +1700,27 @@ u8 *ieee80211_ie_build_ht_cap(u8 *pos, struct ieee80211_sta_ht_cap *ht_cap,
>> return pos;
>> }
>>
>> +u8 *ieee80211_ie_build_vht_cap(u8 *pos, struct ieee80211_sta_vht_cap *vht_cap,
>> + u32 cap)
>
> indentation here & in ieee80211_i.h
>
> [MP] ditto. please explain
>
'u32' should start at same column as 'u8 *pos' in the above line.
Gr. AvS
next prev parent reply other threads:[~2012-06-28 12:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 7:27 [PATCH] cfg80211/mac80211: 802.11ac changes Mahesh Palivela
2012-06-22 7:35 ` Arend van Spriel
2012-06-22 7:37 ` Johannes Berg
2012-06-22 8:17 ` Johannes Berg
2012-06-22 10:11 ` Mahesh Palivela
2012-06-22 10:41 ` Johannes Berg
2012-06-28 10:52 ` Mahesh Palivela
2012-06-28 11:01 ` Johannes Berg
2012-06-28 11:07 ` Johannes Berg
2012-06-28 12:39 ` Mahesh Palivela
2012-06-28 12:53 ` Arend van Spriel [this message]
2012-06-28 12:56 ` 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=4FEC53DE.70602@broadcom.com \
--to=arend@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=maheshp@posedge.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).