From: Arend van Spriel <arend@broadcom.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: kbuild test robot <fengguang.wu@intel.com>,
Hante Meuleman <meuleman@broadcom.com>,
"John W. Linville" <linville@tuxdriver.com>, <kbuild-all@01.org>,
Tony Luck <tony.luck@intel.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [wireless-next:master 169/199] drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c:2469:3: error: implicit declaration of function 'atomic_set_mask'
Date: Mon, 3 Mar 2014 11:53:46 +0100 [thread overview]
Message-ID: <53145F3A.2010203@broadcom.com> (raw)
In-Reply-To: <CAGVrzcaPsaDiBbnbopQTjT_-3ohYWs9HFn-4Y9DL1WJy_A7mzg@mail.gmail.com>
On 02/28/14 23:44, Florian Fainelli wrote:
> 2014-02-28 14:33 GMT-08:00 Arend van Spriel<arend@broadcom.com>:
>> On 02/28/2014 11:26 PM, Florian Fainelli wrote:
>>> 2014-02-28 14:22 GMT-08:00 Arend van Spriel<arend@broadcom.com>:
>>>> On 02/28/2014 11:15 PM, kbuild test robot wrote:
>>>>> tree: git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next.git master
>>>>> head: 3e3831c4fdc53aabf3a56419ef6d96a841c52435
>>>>> commit: c98db0bec72ac7ef127119c1ed962d6f56802b12 [169/199] brcmfmac: Use atomic functions for intstatus update.
>>>>> config: make ARCH=ia64 allmodconfig
>>>>>
>>>>> All error/warnings:
>>>>>
>>>>> drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c: In function 'brcmf_sdio_intr_rstatus':
>>>>>>> drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c:2469:3: error: implicit declaration of function 'atomic_set_mask' [-Werror=implicit-function-declaration]
>>>>> cc1: some warnings being treated as errors
>>>>
>>>> Hi Fengguang,
>>>>
>>>> So atomic_set_mask() is not a generally available function. I thought
>>>> that if the arch does not provide it, the asm-generic implementation is
>>>> used.
>>>
>>> Though so as well.
>>>
>>>> Also it seems the function prototype is not the same for all
>>>> archs. :-(
>>>
>>> This does not sound like it is expected, and this might need fixing,
>>> do you want to tackle this?
>>
>> I got email m68k and ia64 failing. Some implementations are in assembly.
>> It has been (counting...) over 20 years since I did some baby steps in
>> m68k assembly and do not really feel a strong pull to that dark side.
>
> This is supposed to be a generic function that everyone should be able
> to use without knowing the underlying details. Not quite sure why
> those two architectures are different, maybe we should ask Geert and
> Tony about this?
I was about to when I decided to do some more digging. So taking a
closer look at include/asm-generic/atomic.h revealed this:
/*
* Generic C implementation of atomic counter operations. Usable on
* UP systems only. Do not include in machine independent code.
And further down:
#ifdef CONFIG_SMP
/* Force people to define core atomics */
# if !defined(atomic_add_return) || !defined(atomic_sub_return) || \
!defined(atomic_clear_mask) || !defined(atomic_set_mask)
# error "SMP requires a little arch-specific magic"
# endif
#endif
So in these SMP era architecture specific implementations seem required.
IA64 does not provide it (so CONFIG_SMP not supported?) and m68k has
different prototype. Apparently, the comment /* Force people to define
core atomics */ did not fly for all archs (yet) :-p.
Regards,
Arend
next parent reply other threads:[~2014-03-03 10:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53110a73.fVHl0nWfqeLuOaob%fengguang.wu@intel.com>
[not found] ` <53110C1A.60804@broadcom.com>
[not found] ` <CAGVrzcY85PTeQnSf3ptQyC94A3b7FdX9QPxDcSq+UYhgKfWbUg@mail.gmail.com>
[not found] ` <53110EA5.8070503@broadcom.com>
[not found] ` <CAGVrzcaPsaDiBbnbopQTjT_-3ohYWs9HFn-4Y9DL1WJy_A7mzg@mail.gmail.com>
2014-03-03 10:53 ` Arend van Spriel [this message]
2014-03-03 13:21 ` [wireless-next:master 169/199] drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c:2469:3: error: implicit declaration of function 'atomic_set_mask' Geert Uytterhoeven
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=53145F3A.2010203@broadcom.com \
--to=arend@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=geert@linux-m68k.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=meuleman@broadcom.com \
--cc=tony.luck@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