From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Will Deacon <will.deacon@arm.com>,
kbuild test robot <fengguang.wu@intel.com>,
kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: [rcu:rcu/next 30/45] include/linux/compiler.h:343:2: error: implicit declaration of function 'smp_read_barrier_depends'
Date: Fri, 20 Oct 2017 09:50:32 -0700 [thread overview]
Message-ID: <20171020165032.GK3521@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171020124407.gba5a5b6b46mrlj4@lakrids.cambridge.arm.com>
On Fri, Oct 20, 2017 at 01:44:07PM +0100, Mark Rutland wrote:
> On Thu, Oct 19, 2017 at 10:46:57AM -0700, Paul E. McKenney wrote:
[ . . . ]
> > OK, this is now in -rcu on branch rcu/alpha.
> >
> > I then pulled in your commit 8e0bfe6e14e9 ("treewide: kill off ACCESS_ONCE()")
> > on top of this at rcu/alpha-cocci.
> >
> > Again, the smp_read_barrier_depends() waits until this is in-tree.
> >
> > Did I get it right, or did I miss something?
>
> rcu/alpha-cocci looks good to me.
>
> Thanks for organising this!
And both rcu/alpha and rcu/alpha-cocci have been updated with Will's
changes, FYI.
Thanx, Paul
prev parent reply other threads:[~2017-10-20 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-14 23:29 [rcu:rcu/next 30/45] include/linux/compiler.h:343:2: error: implicit declaration of function 'smp_read_barrier_depends' kbuild test robot
2017-10-17 16:14 ` Will Deacon
2017-10-17 16:44 ` Paul E. McKenney
2017-10-19 10:07 ` Will Deacon
2017-10-19 10:27 ` Mark Rutland
2017-10-19 17:46 ` Paul E. McKenney
2017-10-20 12:44 ` Mark Rutland
2017-10-20 16:50 ` Paul E. McKenney [this message]
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=20171020165032.GK3521@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will.deacon@arm.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