linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: "Rafał Miłecki" <rafal@milecki.pl>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"kbuild test robot" <fengguang.wu@intel.com>,
	kbuild-all@01.org, linux-kernel@vger.kernel.org,
	linux-wireless@vger.kernel.org
Subject: Re: drivers/net/wireless/broadcom/brcm80211/brcmfmac/debug.c:58:6: error: redefinition of 'brcmf_debugfs_init'
Date: Thu, 16 Feb 2017 15:18:48 +0200	[thread overview]
Message-ID: <8737fe46kn.fsf@codeaurora.org> (raw)
In-Reply-To: <8ff44e41-97c7-4ae5-6850-65ad407fd788@broadcom.com> (Arend Van Spriel's message of "Thu, 16 Feb 2017 11:30:56 +0100")

Arend Van Spriel <arend.vanspriel@broadcom.com> writes:

> On 16-2-2017 11:01, Kalle Valo wrote:
>> Arend Van Spriel <arend.vanspriel@broadcom.com> writes:
>>=20
>>> On 16-2-2017 10:39, Rafa=C5=82 Mi=C5=82ecki wrote:
>>>> On 02/16/2017 10:31 AM, Kalle Valo wrote:
>>>>> (Adding linux-wireless)
>>>>>
>>>>> Arend or Rafa=C5=82, would you be able to look at this build problem?=
 Kbuild
>>>>> found the build errors below, apparently a very old issue. It just
>>>>> blames me now because I moved the driver to a new directory :)
>>>
>>> It is a very old issue. The thing is that the issue can not really occur
>>> because we have this:
>>>
>>> # common flags
>>> subdir-ccflags-$(CONFIG_BRCMDBG)        +=3D -DDEBUG
>>>
>>> in drivers/net/wireless/broadcom/brcm80211/Makefile. So no clue what
>>> happens in the "kbuild test robot" scenario.
>>=20
>> I actually tried to reproduce this with kbuild bot's instructions and
>> was surprised to see that the build worked ok for me. So the issue is
>> not that simple.
>
> Hi Kalle,
>
> Here is the old email exchange we had about this [1]. In my opinion this
> is a Kbuild issue that needs to be looked into.
>
> Regards,
> Arend
>
> [1] http://www.spinics.net/lists/linux-wireless/msg142122.html

Heh, I had completely forgotten that we had discussed this before :)

Fengguang and the kbuild bot team, do you have any ideas why only the
bot is seeing this?

--=20
Kalle Valo

  parent reply	other threads:[~2017-02-16 13:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201702071839.Ej9MjmlI%fengguang.wu@intel.com>
     [not found] ` <ce7467a9-12d5-f64e-8b59-f9581db9f7c8@infradead.org>
2017-02-16  9:31   ` drivers/net/wireless/broadcom/brcm80211/brcmfmac/debug.c:58:6: error: redefinition of 'brcmf_debugfs_init' 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 [this message]
2017-02-17  1:45               ` Fengguang Wu

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=8737fe46kn.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=arend.vanspriel@broadcom.com \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rafal@milecki.pl \
    --cc=rdunlap@infradead.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).