From: kbuild test robot <fengguang.wu@intel.com>
To: Johannes Berg <johannes.berg@intel.com>
Cc: kbuild-all@01.org, linux-wireless@vger.kernel.org
Subject: [mac80211-next:vht-he 11/14] net/mac80211/vht.c:307:4: error: expected ')' before 'break'
Date: Wed, 15 Feb 2017 22:33:05 +0800 [thread overview]
Message-ID: <201702152203.XmplHNyO%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1650 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git vht-he
head: 860f13022f1783b9ac8e5ce4aed06ac9dbf110cb
commit: 5df804200a23280b5c7955996897a5a235a96cb7 [11/14] mac80211: copy VHT EXT NSS BW Support/Capable data to station
config: x86_64-randconfig-x000-201707 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
git checkout 5df804200a23280b5c7955996897a5a235a96cb7
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
net/mac80211/vht.c: In function 'ieee80211_vht_cap_ie_to_sta_vht_cap':
>> net/mac80211/vht.c:307:4: error: expected ')' before 'break'
break;
^~~~~
>> net/mac80211/vht.c:316:2: error: expected expression before '}' token
}
^
vim +307 net/mac80211/vht.c
301 break;
302 default:
303 sta->cur_max_bandwidth = IEEE80211_STA_RX_BW_80;
304
305 if (!(vht_cap->vht_mcs.tx_highest &
306 cpu_to_le16(IEEE80211_VHT_EXT_NSS_BW_CAPABLE))
> 307 break;
308
309 /*
310 * If this is non-zero, then it does support 160 MHz after all,
311 * in one form or the other. We don't distinguish here (or even
312 * above) between 160 and 80+80 yet.
313 */
314 if (cap_info & IEEE80211_VHT_CAP_EXT_NSS_BW_MASK)
315 sta->cur_max_bandwidth = IEEE80211_STA_RX_BW_160;
> 316 }
317
318 sta->sta.bandwidth = ieee80211_sta_cur_vht_bw(sta);
319
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 26999 bytes --]
reply other threads:[~2017-02-15 14:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201702152203.XmplHNyO%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=johannes.berg@intel.com \
--cc=kbuild-all@01.org \
--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