From: Randy Dunlap <rdunlap@infradead.org>
To: kbuild test robot <fengguang.wu@intel.com>,
Kalle Valo <kvalo@codeaurora.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: drivers/net/wireless/broadcom/brcm80211/brcmfmac/debug.c:58:6: error: redefinition of 'brcmf_debugfs_init'
Date: Tue, 7 Feb 2017 08:31:39 -0800 [thread overview]
Message-ID: <ce7467a9-12d5-f64e-8b59-f9581db9f7c8@infradead.org> (raw)
In-Reply-To: <201702071839.Ej9MjmlI%fengguang.wu@intel.com>
On 02/07/17 02:02, kbuild test robot wrote:
> Hi Kalle,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 8b1b41ee74f9712c355d66dc105bbea663ae0afd
> commit: 05491d2ccf20b20a1375303441fbbfbd12b24a4f brcm80211: move under broadcom vendor directory
> date: 1 year, 3 months ago
> config: mips-allyesconfig (attached as .config)
> compiler: mips-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 05491d2ccf20b20a1375303441fbbfbd12b24a4f
> # save the attached .config to linux build tree
> make.cross ARCH=mips
>
> All errors (new ones prefixed by >>):
when both:
CONFIG_BRCM_TRACING=y
CONFIG_BRCMDBG=y
but DEBUG is not defined.
I think it would help if CONFIG_BRCMDBG set DEBUG
or if some of the tests for DEBUG used CONFIG_BRCMDBG instead.
--
~Randy
next prev parent reply other threads:[~2017-02-07 16:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 10:02 drivers/net/wireless/broadcom/brcm80211/brcmfmac/debug.c:58:6: error: redefinition of 'brcmf_debugfs_init' kbuild test robot
2017-02-07 16:31 ` Randy Dunlap [this message]
2017-02-16 9:31 ` Kalle Valo
2017-02-16 9:39 ` Rafał Miłecki
2017-02-16 9:53 ` Arend Van Spriel
2017-02-16 10:01 ` Kalle Valo
2017-02-16 10:30 ` Arend Van Spriel
2017-02-16 13:08 ` [kbuild-all] " Fengguang Wu
2017-02-16 13:18 ` Kalle Valo
2017-02-17 1:45 ` [kbuild-all] " Fengguang Wu
-- strict thread matches above, loose matches on Subject: below --
2016-12-03 10:00 kbuild test robot
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=ce7467a9-12d5-f64e-8b59-f9581db9f7c8@infradead.org \
--to=rdunlap@infradead.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).