From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Johannes Berg <johannes@sipsolutions.net>,
kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-wireless@vger.kernel.org
Subject: Re: [mac80211:master 6/11] net/mac80211/tx.c:3581:3: error: implicit declaration of function 'sk_pacing_shift_update'; did you mean 'sk_incoming_cpu_update'?
Date: Mon, 19 Feb 2018 15:17:09 +0100 [thread overview]
Message-ID: <87d1115aje.fsf@toke.dk> (raw)
In-Reply-To: <1519049086.16723.21.camel@sipsolutions.net>
Johannes Berg <johannes@sipsolutions.net> writes:
> On Mon, 2018-02-19 at 21:51 +0800, kbuild test robot wrote:
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211.git master
>> head: 49241828e8ed0b0a3dc73466d5bc562ae90acfd6
>> commit: 96bd4b9e4a44c6c1da93fd3e48bd8eb1b332584a [6/11] mac80211: Adjust TSQ pacing shift
>> config: x86_64-randconfig-x011-201807 (attached as .config)
>> compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
>> reproduce:
>> git checkout 96bd4b9e4a44c6c1da93fd3e48bd8eb1b332584a
>> # save the attached .config to linux build tree
>> make ARCH=x86_64
>>
>> All errors (new ones prefixed by >>):
>>
>> net/mac80211/tx.c: In function '__ieee80211_subif_start_xmit':
>> > > net/mac80211/tx.c:3581:3: error: implicit declaration of function 'sk_pacing_shift_update'; did you mean 'sk_incoming_cpu_update'? [-Werror=implicit-function-declaration]
>>
>> sk_pacing_shift_update(skb->sk, 8);
>> ^~~~~~~~~~~~~~~~~~~~~~
>
> Yeah, umm, I accidentally applied this on the wrong tree - already
> fixed.
Aha, gotcha. Was scratching my head there for a while ;)
-Toke
prev parent reply other threads:[~2018-02-19 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 13:51 [mac80211:master 6/11] net/mac80211/tx.c:3581:3: error: implicit declaration of function 'sk_pacing_shift_update'; did you mean 'sk_incoming_cpu_update'? kbuild test robot
2018-02-19 14:04 ` Johannes Berg
2018-02-19 14:17 ` Toke Høiland-Jørgensen [this message]
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=87d1115aje.fsf@toke.dk \
--to=toke@toke.dk \
--cc=fengguang.wu@intel.com \
--cc=johannes@sipsolutions.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.