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 15:56:39 +0800 [thread overview]
Message-ID: <201704061509.dEp1JEgq%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170405161810.30671-1-toke@toke.dk>
[-- Attachment #1: Type: text/plain, Size: 2033 bytes --]
Hi Toke,
[auto build test ERROR on mac80211/master]
[also build test ERROR 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
config: i386-randconfig-x019-201714 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> net//mac80211/sta_info.c:2308:20: error: static declaration of 'sta_update_codel_params' follows non-static declaration
static inline void sta_update_codel_params(struct sta_info *sta, u32 thr)
^~~~~~~~~~~~~~~~~~~~~~~
In file included from net//mac80211/ieee80211_i.h:35:0,
from net//mac80211/sta_info.c:25:
net//mac80211/sta_info.h:727:6: note: previous declaration of 'sta_update_codel_params' was here
void sta_update_codel_params(struct sta_info *sta, u32 thr);
^~~~~~~~~~~~~~~~~~~~~~~
--
net//mac80211/tx.c: In function 'fq_tin_dequeue_func':
>> net//mac80211/tx.c:1352:26: error: 'struct codel_params' has no member named 'params'
cparams = &sta->cparams.params;
^
vim +/sta_update_codel_params +2308 net//mac80211/sta_info.c
2302
2303 if (time_after(stats->last_rx, sta->status_stats.last_ack))
2304 return stats->last_rx;
2305 return sta->status_stats.last_ack;
2306 }
2307
> 2308 static inline void sta_update_codel_params(struct sta_info *sta, u32 thr)
2309 {
2310 if (!sta->sdata->local->ops->wake_tx_queue)
2311 return;
---
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: 33136 bytes --]
next prev parent reply other threads:[~2017-04-06 7:57 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 [this message]
2017-04-06 8:45 ` kbuild test robot
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=201704061509.dEp1JEgq%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