linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: kbuild test robot <lkp@intel.com>,
	kbuild-all@01.org,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 3/5] nl80211: add support for gscan
Date: Thu, 17 Nov 2016 13:40:42 +0100	[thread overview]
Message-ID: <014498fc-8f54-c07e-da5c-8dae0e577a7b@broadcom.com> (raw)
In-Reply-To: <201611172006.xRJ9na1r%fengguang.wu@intel.com>

On 17-11-2016 13:10, kbuild test robot wrote:
> Hi Arend,
> 
> [auto build test ERROR on mac80211-next/master]
> [also build test ERROR on next-20161117]
> [cannot apply to v4.9-rc5]
> [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/Arend-van-Spriel/nl80211-add-support-for-g-scan/20161117-194818
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git master
> config: i386-randconfig-x004-201646 (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 

Shuffled the patches while rebasing. Not nice. Will fix it.

Regards,
Arend

> Note: the linux-review/Arend-van-Spriel/nl80211-add-support-for-g-scan/20161117-194818 HEAD 407f604bb543a049c99ae0f9974943f1c64ea880 builds fine.
>       It only hurts bisectibility.
> 
> All errors (new ones prefixed by >>):
> 
>    net/wireless/scan.c: In function '__cfg80211_stop_gscan':
>>> net/wireless/scan.c:358:2: error: implicit declaration of function 'nl80211_send_scan_event' [-Werror=implicit-function-declaration]
>      nl80211_send_scan_event(rdev, dev, NL80211_CMD_GSCAN_STOPPED);
>      ^~~~~~~~~~~~~~~~~~~~~~~
>    cc1: some warnings being treated as errors
> --
>    net/wireless/nl80211.c: In function 'nl80211_start_gscan':
>>> net/wireless/nl80211.c:12167:2: error: implicit declaration of function 'nl80211_send_scan_event' [-Werror=implicit-function-declaration]
>      nl80211_send_scan_event(rdev, dev,
>      ^~~~~~~~~~~~~~~~~~~~~~~
>    cc1: some warnings being treated as errors
> 
> vim +/nl80211_send_scan_event +358 net/wireless/scan.c
> 
>    352		if (!driver_initiated) {
>    353			int err = rdev_stop_gscan(rdev, dev);
>    354			if (err)
>    355				return err;
>    356		}
>    357	
>  > 358		nl80211_send_scan_event(rdev, dev, NL80211_CMD_GSCAN_STOPPED);
>    359	
>    360		RCU_INIT_POINTER(rdev->gscan_req, NULL);
>    361		kfree_rcu(gscan_req, rcu_head);
> 
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation
> 

  reply	other threads:[~2016-11-17 14:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17 11:39 [RFC 0/5] nl80211: add support for g-scan Arend van Spriel
2016-11-17 11:39 ` [PATCH 1/5] nl80211: allow reporting RTT information in scan results Arend van Spriel
2016-11-17 16:15   ` Dan Williams
2016-11-17 19:50     ` Arend Van Spriel
2016-11-17 11:39 ` [PATCH 2/5] nl80211: add reporting of gscan capabilities Arend van Spriel
2016-11-17 14:20   ` kbuild test robot
2016-11-17 11:39 ` [PATCH 3/5] nl80211: add support for gscan Arend van Spriel
2016-11-17 12:10   ` kbuild test robot
2016-11-17 12:40     ` Arend Van Spriel [this message]
2016-11-17 16:32   ` kbuild test robot
2016-11-17 11:39 ` [PATCH 4/5] nl80211: rename some notification functions Arend van Spriel
2016-11-17 11:39 ` [PATCH 5/5] nl80211: add driver api for gscan notifications Arend van Spriel
2016-11-17 12:11   ` Arend Van Spriel

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=014498fc-8f54-c07e-da5c-8dae0e577a7b@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=johannes@sipsolutions.net \
    --cc=kbuild-all@01.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lkp@intel.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).