Linux wireless drivers development
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Johannes Berg <johannes.berg@intel.com>
Cc: kbuild-all@01.org, linux-wireless@vger.kernel.org
Subject: [mac80211-next:regulatory 24/24] net/wireless/reg.c:719:6: error: 'CONFIG_CFG80211_EXTRA_REGDB_KEYDIR' undeclared
Date: Fri, 6 Oct 2017 21:23:49 +0800	[thread overview]
Message-ID: <201710062146.zq2pL7ih%fengguang.wu@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git regulatory
head:   bdf90273d9eb56ce431a1d44a5b6c9257de460a6
commit: bdf90273d9eb56ce431a1d44a5b6c9257de460a6 [24/24] cfg80211: implement regdb signature checking
config: x86_64-allyesdebian (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        git checkout bdf90273d9eb56ce431a1d44a5b6c9257de460a6
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   net/wireless/reg.c: In function 'load_builtin_regdb_keys':
>> net/wireless/reg.c:719:6: error: 'CONFIG_CFG80211_EXTRA_REGDB_KEYDIR' undeclared (first use in this function)
     if (CONFIG_CFG80211_EXTRA_REGDB_KEYDIR[0] != '\0')
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   net/wireless/reg.c:719:6: note: each undeclared identifier is reported only once for each function it appears in

vim +/CONFIG_CFG80211_EXTRA_REGDB_KEYDIR +719 net/wireless/reg.c

   702	
   703	static int __init load_builtin_regdb_keys(void)
   704	{
   705		builtin_regdb_keys =
   706			keyring_alloc(".builtin_regdb_keys",
   707				      KUIDT_INIT(0), KGIDT_INIT(0), current_cred(),
   708				      ((KEY_POS_ALL & ~KEY_POS_SETATTR) |
   709				      KEY_USR_VIEW | KEY_USR_READ | KEY_USR_SEARCH),
   710				      KEY_ALLOC_NOT_IN_QUOTA, NULL, NULL);
   711		if (IS_ERR(builtin_regdb_keys))
   712			return PTR_ERR(builtin_regdb_keys);
   713	
   714		pr_notice("Loading compiled-in X.509 certificates for regulatory database\n");
   715	
   716	#ifdef CONFIG_CFG80211_USE_KERNEL_REGDB_KEYS
   717		load_keys_from_buffer(shipped_regdb_certs, shipped_regdb_certs_len);
   718	#endif
 > 719		if (CONFIG_CFG80211_EXTRA_REGDB_KEYDIR[0] != '\0')
   720			load_keys_from_buffer(extra_regdb_certs, extra_regdb_certs_len);
   721	
   722		return 0;
   723	}
   724	

---
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: 39651 bytes --]

                 reply	other threads:[~2017-10-06 13:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201710062146.zq2pL7ih%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=johannes.berg@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox