From: kbuild test robot <lkp@intel.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: kbuild-all@01.org, make-wifi-fast@lists.bufferbloat.net,
linux-wireless@vger.kernel.org,
"Toke Høiland-Jørgensen" <toke@toke.dk>
Subject: Re: [Make-wifi-fast] [PATCH v2] mac80211: Dynamically set CoDel parameters per station
Date: Thu, 6 Apr 2017 16:45:45 +0800 [thread overview]
Message-ID: <201704061614.wcNp1XwD%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170405161810.30671-1-toke@toke.dk>
[-- Attachment #1: Type: text/plain, Size: 4003 bytes --]
Hi Toke,
[auto build test WARNING on mac80211/master]
[also build test WARNING on v4.11-rc5 next-20170406]
[cannot apply to mac80211-next/master]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Toke-H-iland-J-rgensen/mac80211-Dynamically-set-CoDel-parameters-per-station/20170406-152423
base: https://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211.git master
reproduce: make htmldocs
All warnings (new ones prefixed by >>):
>> include/net/mac80211.h:4198: warning: No description found for parameter 'pubsta'
>> include/net/mac80211.h:4198: warning: Excess function parameter 'sta' description in 'ieee80211_sta_set_expected_throughput'
>> include/net/mac80211.h:4198: warning: No description found for parameter 'pubsta'
>> include/net/mac80211.h:4198: warning: Excess function parameter 'sta' description in 'ieee80211_sta_set_expected_throughput'
>> include/net/mac80211.h:4198: warning: No description found for parameter 'pubsta'
>> include/net/mac80211.h:4198: warning: Excess function parameter 'sta' description in 'ieee80211_sta_set_expected_throughput'
>> include/net/mac80211.h:4198: warning: No description found for parameter 'pubsta'
>> include/net/mac80211.h:4198: warning: Excess function parameter 'sta' description in 'ieee80211_sta_set_expected_throughput'
>> include/net/mac80211.h:4198: warning: No description found for parameter 'pubsta'
>> include/net/mac80211.h:4198: warning: Excess function parameter 'sta' description in 'ieee80211_sta_set_expected_throughput'
>> include/net/mac80211.h:4198: warning: No description found for parameter 'pubsta'
>> include/net/mac80211.h:4198: warning: Excess function parameter 'sta' description in 'ieee80211_sta_set_expected_throughput'
>> include/net/mac80211.h:4198: warning: No description found for parameter 'pubsta'
>> include/net/mac80211.h:4198: warning: Excess function parameter 'sta' description in 'ieee80211_sta_set_expected_throughput'
>> include/net/mac80211.h:4198: warning: No description found for parameter 'pubsta'
>> include/net/mac80211.h:4198: warning: Excess function parameter 'sta' description in 'ieee80211_sta_set_expected_throughput'
>> include/net/mac80211.h:4198: warning: No description found for parameter 'pubsta'
>> include/net/mac80211.h:4198: warning: Excess function parameter 'sta' description in 'ieee80211_sta_set_expected_throughput'
>> include/net/mac80211.h:4198: warning: No description found for parameter 'pubsta'
>> include/net/mac80211.h:4198: warning: Excess function parameter 'sta' description in 'ieee80211_sta_set_expected_throughput'
vim +/pubsta +4198 include/net/mac80211.h
4182
4183 /**
4184 * ieee80211_sta_set_expected_throughput - set the expected throughput for a
4185 * station
4186 *
4187 * Call this function to notify mac80211 about a change in expected throughput
4188 * to a station. A driver for a device that does rate control in firmware can
4189 * call this function when the expected throughput estimate towards a station
4190 * changes. The information is used to tune the CoDel AQM applied to traffic
4191 * going towards that station (which can otherwise be too aggressive and cause
4192 * slow stations to starve).
4193 *
4194 * @sta: the station to set throughput for.
4195 * @thr: the current expected throughput in kbps.
4196 */
4197 void ieee80211_sta_set_expected_throughput(struct ieee80211_sta *pubsta,
> 4198 u32 thr);
4199
4200 /**
4201 * ieee80211_tx_status - transmit status callback
4202 *
4203 * Call this function for all transmitted frames after they have been
4204 * transmitted. It is permissible to not call this function for
4205 * multicast frames but this can affect statistics.
4206 *
---
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: 6576 bytes --]
next prev parent reply other threads:[~2017-04-06 8:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-10 19:33 [Make-wifi-fast] [PATCH] " Toke Høiland-Jørgensen
2016-09-10 19:54 ` Jim Gettys
2016-09-10 20:09 ` Toke Høiland-Jørgensen
2016-09-11 3:16 ` Loganaden Velvindron
2016-09-11 0:09 ` kbuild test robot
2017-04-05 16:18 ` [Make-wifi-fast] [PATCH v2] " Toke Høiland-Jørgensen
2017-04-06 7:56 ` kbuild test robot
2017-04-06 8:45 ` kbuild test robot [this message]
2017-04-06 9:38 ` [Make-wifi-fast] [PATCH v3] " Toke Høiland-Jørgensen
2017-04-06 10:51 ` Eric Dumazet
2017-04-06 15:58 ` Toke Høiland-Jørgensen
2017-04-13 18:26 ` Dave Taht
2017-05-17 14:06 ` Johannes Berg
2017-05-19 9:27 ` Toke Høiland-Jørgensen
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
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201704061614.wcNp1XwD%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-wireless@vger.kernel.org \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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