From: Jason Low <jason.low2@hp.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will.deacon@arm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, mingo@redhat.com,
paulmck@linux.vnet.ibm.com, terry.rudd@hpe.com,
waiman.long@hpe.com, boqun.feng@gmail.com, dave@stgolabs.net,
jason.low2@hp.com
Subject: Re: [PATCH] MCS spinlock: Use smp_cond_load_acquire()
Date: Tue, 12 Apr 2016 16:40:55 -0700 [thread overview]
Message-ID: <1460504455.2465.141.camel@j-VirtualBox> (raw)
In-Reply-To: <201604130658.n9ttDvqp%fengguang.wu@intel.com>
On Wed, 2016-04-13 at 06:39 +0800, kbuild test robot wrote:
> Hi Jason,
>
> [auto build test ERROR on v4.6-rc3]
> [also build test ERROR on next-20160412]
> [cannot apply to tip/core/locking]
> [if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
>
> url: https://github.com/0day-ci/linux/commits/Jason-Low/MCS-spinlock-Use-smp_cond_load_acquire/20160413-053726
> config: i386-randconfig-s0-201615 (attached as .config)
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All error/warnings (new ones prefixed by >>):
>
> In file included from kernel/locking/qspinlock.c:70:0:
> kernel/locking/mcs_spinlock.h: In function 'mcs_spin_lock':
> >> kernel/locking/mcs_spinlock.h:31:2: error: implicit declaration of function 'smp_cond_load_acquire' [-Werror=implicit-function-declaration]
> smp_cond_load_acquire(&l, VAL); \
Hello,
This patch depends on the "smp_cond_load_acquire + cmpwait" patchset,
which is in:
git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git locking/rfc
next prev parent reply other threads:[~2016-04-12 23:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 21:29 [PATCH] MCS spinlock: Use smp_cond_load_acquire() Jason Low
2016-04-12 22:39 ` kbuild test robot
2016-04-12 23:40 ` Jason Low [this message]
2016-04-12 23:50 ` Jason Low
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=1460504455.2465.141.camel@j-VirtualBox \
--to=jason.low2@hp.com \
--cc=boqun.feng@gmail.com \
--cc=dave@stgolabs.net \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=terry.rudd@hpe.com \
--cc=torvalds@linux-foundation.org \
--cc=waiman.long@hpe.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