All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	"John W. Linville" <linville@tuxdriver.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Hante Meuleman <meuleman@broadcom.com>
Subject: Re: linux-next: build failure after merge of the wireless-next tree
Date: Thu, 6 Mar 2014 09:53:58 +0100	[thread overview]
Message-ID: <531837A6.8090406@broadcom.com> (raw)
In-Reply-To: <20140306134332.0c3f12ec6849d1b2ccefda6e@canb.auug.org.au>

On 03/06/2014 03:43 AM, Stephen Rothwell wrote:
> Hi John,
> 
> After merging the wireless-next tree, today's linux-next build
> (arm multi_v7_defconfig) failed like this:
> 
> drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c: In function
> 'brcmf_sdio_intr_rstatus': 
> drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c:2464:3: error:
> implicit declaration of function 'atomic_set_mask'
> [-Werror=implicit-function-declaration]
> 
> Caused by commit c98db0bec72a ("brcmfmac: Use atomic functions for 
> intstatus update").  Arm does not seem to provide
> atomic_set_mask()?
> 
> I reverted that commit for today.

That is fine. The kbuild robot also found issue with this function on
other archs. I must say I am surprised as this code fragment in
asm-generic/atomic.h suggests it is needed for SMP to work (?):

 20 #ifdef CONFIG_SMP
 21 /* Force people to define core atomics */
 22 # if !defined(atomic_add_return) || !defined(atomic_sub_return) || \
 23      !defined(atomic_clear_mask) || !defined(atomic_set_mask)
 24 #  error "SMP requires a little arch-specific magic"
 25 # endif
 26 #endif

Maybe this requirement is no longer valid. Anyway. I will sent revert
patch and replacement to John.

Thanks,
Arend

WARNING: multiple messages have this Message-ID (diff)
From: Arend van Spriel <arend@broadcom.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	"John W. Linville" <linville@tuxdriver.com>
Cc: <linux-next@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"Hante Meuleman" <meuleman@broadcom.com>
Subject: Re: linux-next: build failure after merge of the wireless-next tree
Date: Thu, 6 Mar 2014 09:53:58 +0100	[thread overview]
Message-ID: <531837A6.8090406@broadcom.com> (raw)
In-Reply-To: <20140306134332.0c3f12ec6849d1b2ccefda6e@canb.auug.org.au>

On 03/06/2014 03:43 AM, Stephen Rothwell wrote:
> Hi John,
> 
> After merging the wireless-next tree, today's linux-next build
> (arm multi_v7_defconfig) failed like this:
> 
> drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c: In function
> 'brcmf_sdio_intr_rstatus': 
> drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c:2464:3: error:
> implicit declaration of function 'atomic_set_mask'
> [-Werror=implicit-function-declaration]
> 
> Caused by commit c98db0bec72a ("brcmfmac: Use atomic functions for 
> intstatus update").  Arm does not seem to provide
> atomic_set_mask()?
> 
> I reverted that commit for today.

That is fine. The kbuild robot also found issue with this function on
other archs. I must say I am surprised as this code fragment in
asm-generic/atomic.h suggests it is needed for SMP to work (?):

 20 #ifdef CONFIG_SMP
 21 /* Force people to define core atomics */
 22 # if !defined(atomic_add_return) || !defined(atomic_sub_return) || \
 23      !defined(atomic_clear_mask) || !defined(atomic_set_mask)
 24 #  error "SMP requires a little arch-specific magic"
 25 # endif
 26 #endif

Maybe this requirement is no longer valid. Anyway. I will sent revert
patch and replacement to John.

Thanks,
Arend

  reply	other threads:[~2014-03-06  8:53 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06  2:43 linux-next: build failure after merge of the wireless-next tree Stephen Rothwell
2014-03-06  8:53 ` Arend van Spriel [this message]
2014-03-06  8:53   ` Arend van Spriel
  -- strict thread matches above, loose matches on Subject: below --
2025-01-16  2:08 Stephen Rothwell
2025-01-16  5:49 ` Ping-Ke Shih
2025-01-16 19:30   ` Kalle Valo
2024-10-09  1:04 Stephen Rothwell
2024-10-09  7:04 ` Johannes Berg
2014-09-08  8:42 Stephen Rothwell
2014-09-09 23:28 ` Stephen Rothwell
2014-09-09 23:28   ` Stephen Rothwell
2014-09-09 23:37   ` David Miller
2014-09-10 17:46     ` John W. Linville
2014-07-16  3:28 Stephen Rothwell
2014-07-16 14:09 ` John W. Linville
2014-04-23  3:47 Stephen Rothwell
2014-04-23 20:54 ` Bing Zhao
2014-03-06  2:24 Stephen Rothwell
2014-02-25  2:35 Stephen Rothwell
2014-02-25 19:07 ` John W. Linville
2014-02-25 20:47   ` Stephen Rothwell
2014-03-04 23:16     ` Stephen Rothwell
2014-03-04 23:21       ` Stephen Rothwell
2014-03-04 23:49         ` Greg KH
2014-02-13  2:19 Stephen Rothwell
2014-02-13  2:22 ` Stephen Rothwell
2014-02-13 17:31 ` Paul Gortmaker
2014-02-13 18:22   ` Paul Gortmaker
2014-02-13 18:28     ` Greg KH
2013-07-23  1:32 Stephen Rothwell
2013-07-23  7:24 ` Hauke Mehrtens
2013-04-02  2:34 Stephen Rothwell
2013-04-02  3:07 ` Larry Finger
2013-04-02  3:31   ` Stephen Rothwell
2013-04-02  4:07     ` Larry Finger
2012-04-12  2:24 Stephen Rothwell
2012-04-12  2:24 ` Stephen Rothwell
2011-12-20  2:18 Stephen Rothwell
2011-12-20  2:42 ` Luis R. Rodriguez
2011-12-20  2:57   ` Stephen Rothwell
2011-12-20  3:24     ` Luis R. Rodriguez
2011-11-22  3:35 Stephen Rothwell
2011-11-22  8:03 ` Stanislaw Gruszka

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=531837A6.8090406@broadcom.com \
    --to=arend@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=meuleman@broadcom.com \
    --cc=sfr@canb.auug.org.au \
    /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.