From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Richard Weinberger <richard@nod.at>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: linux-next: Tree for Jan 15 (um, rcu)
Date: Wed, 15 Jan 2014 08:21:37 -0800 [thread overview]
Message-ID: <52D6B591.3070707@infradead.org> (raw)
In-Reply-To: <20140115185545.497c14923814b6ecaa540d9f@canb.auug.org.au>
On 01/14/2014 11:55 PM, Stephen Rothwell wrote:
> Hi all,
>
> This tree fails (more than usual) the powerpc allyesconfig build.
>
> Changes since 20140114:
>
on i386 and/or x86_64 defconfigs:
CC arch/um/kernel/asm-offsets.s
In file included from include/linux/sched.h:43:0,
from arch/x86/um/shared/sysdep/kernel-offsets.h:2,
from arch/um/kernel/asm-offsets.c:1:
include/linux/rculist.h: In function '__list_add_rcu':
include/linux/rculist.h:54:2: error: implicit declaration of function 'smp_store_release' [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[2]: *** [arch/um/kernel/asm-offsets.s] Error 1
--
~Randy
next prev parent reply other threads:[~2014-01-15 16:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 7:55 linux-next: Tree for Jan 15 Stephen Rothwell
2014-01-15 16:21 ` Randy Dunlap [this message]
2014-01-15 19:35 ` [PATCH] um: Include generic barrier.h Richard Weinberger
2014-01-15 20:03 ` [uml-devel] " Geert Uytterhoeven
2014-01-15 19:39 ` linux-next: Tree for Jan 15 (um, rcu) Richard Weinberger
2014-01-15 20:50 ` Stephen Rothwell
2014-01-15 20:57 ` Richard Weinberger
2014-01-15 23:24 ` linux-next: Tree for Jan 15 (infiniband: ocrdma) Randy Dunlap
2014-01-15 23:39 ` linux-next: Tree for Jan 15 (netfilter: nft_reject) Randy Dunlap
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=52D6B591.3070707@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=richard@nod.at \
--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 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).