All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Peter Oh <poh@qca.qualcomm.com>
Cc: kbuild-all@01.org, ath10k@lists.infradead.org,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath10k: Enable VHT for Mesh
Date: Fri, 13 Nov 2015 08:43:19 +0800	[thread overview]
Message-ID: <201511130809.yFUvfsvJ%fengguang.wu@intel.com> (raw)
In-Reply-To: <1447366355-4900-1-git-send-email-poh@qca.qualcomm.com>

[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]

Hi Peter,

[auto build test ERROR on wireless-drivers-next/master]
[also build test ERROR on v4.3 next-20151112]

url:    https://github.com/0day-ci/linux/commits/Peter-Oh/ath10k-Enable-VHT-for-Mesh/20151113-061427
base:   https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git master
config: i386-allmodconfig (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   drivers/net/wireless/ath/ath10k/mac.c: In function 'ath10k_mac_register':
>> drivers/net/wireless/ath/ath10k/mac.c:7262:39: error: 'NL80211_EXT_FEATURE_VHT_MESH' undeclared (first use in this function)
     wiphy_ext_feature_set(ar->hw->wiphy, NL80211_EXT_FEATURE_VHT_MESH);
                                          ^
   drivers/net/wireless/ath/ath10k/mac.c:7262:39: note: each undeclared identifier is reported only once for each function it appears in

vim +/NL80211_EXT_FEATURE_VHT_MESH +7262 drivers/net/wireless/ath/ath10k/mac.c

  7256		if (ret) {
  7257			ath10k_warn(ar, "failed to init wow: %d\n", ret);
  7258			goto err_free;
  7259		}
  7260	
  7261		wiphy_ext_feature_set(ar->hw->wiphy, NL80211_EXT_FEATURE_VHT_IBSS);
> 7262		wiphy_ext_feature_set(ar->hw->wiphy, NL80211_EXT_FEATURE_VHT_MESH);
  7263	
  7264		/*
  7265		 * on LL hardware queues are managed entirely by the FW

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 51725 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: Peter Oh <poh@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, kbuild-all@01.org,
	ath10k@lists.infradead.org
Subject: Re: [PATCH] ath10k: Enable VHT for Mesh
Date: Fri, 13 Nov 2015 08:43:19 +0800	[thread overview]
Message-ID: <201511130809.yFUvfsvJ%fengguang.wu@intel.com> (raw)
In-Reply-To: <1447366355-4900-1-git-send-email-poh@qca.qualcomm.com>

[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]

Hi Peter,

[auto build test ERROR on wireless-drivers-next/master]
[also build test ERROR on v4.3 next-20151112]

url:    https://github.com/0day-ci/linux/commits/Peter-Oh/ath10k-Enable-VHT-for-Mesh/20151113-061427
base:   https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git master
config: i386-allmodconfig (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   drivers/net/wireless/ath/ath10k/mac.c: In function 'ath10k_mac_register':
>> drivers/net/wireless/ath/ath10k/mac.c:7262:39: error: 'NL80211_EXT_FEATURE_VHT_MESH' undeclared (first use in this function)
     wiphy_ext_feature_set(ar->hw->wiphy, NL80211_EXT_FEATURE_VHT_MESH);
                                          ^
   drivers/net/wireless/ath/ath10k/mac.c:7262:39: note: each undeclared identifier is reported only once for each function it appears in

vim +/NL80211_EXT_FEATURE_VHT_MESH +7262 drivers/net/wireless/ath/ath10k/mac.c

  7256		if (ret) {
  7257			ath10k_warn(ar, "failed to init wow: %d\n", ret);
  7258			goto err_free;
  7259		}
  7260	
  7261		wiphy_ext_feature_set(ar->hw->wiphy, NL80211_EXT_FEATURE_VHT_IBSS);
> 7262		wiphy_ext_feature_set(ar->hw->wiphy, NL80211_EXT_FEATURE_VHT_MESH);
  7263	
  7264		/*
  7265		 * on LL hardware queues are managed entirely by the FW

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 51725 bytes --]

[-- Attachment #3: Type: text/plain, Size: 146 bytes --]

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2015-11-13  0:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 22:12 [PATCH] ath10k: Enable VHT for Mesh Peter Oh
2015-11-12 22:12 ` Peter Oh
2015-11-13  0:43 ` kbuild test robot [this message]
2015-11-13  0:43   ` kbuild test robot
  -- strict thread matches above, loose matches on Subject: below --
2015-11-12 17:47 Peter Oh
2015-11-12 17:47 ` Peter Oh

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=201511130809.yFUvfsvJ%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=ath10k@lists.infradead.org \
    --cc=kbuild-all@01.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=poh@qca.qualcomm.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 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.