From: Josh Poimboeuf <jpoimboe@redhat.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Kees Cook <keescook@chromium.org>,
kbuild-all@01.org, linux-kernel@vger.kernel.org,
tipbuild@zytor.com, Ingo Molnar <mingo@kernel.org>
Subject: Re: [tip:locking/core 36/40] arch/x86/include/asm/refcount.h:21:2: error: expected ':' or ')' before 'ASM_UNREACHABLE'
Date: Thu, 17 Aug 2017 07:55:53 -0500 [thread overview]
Message-ID: <20170817125553.hhw2nbft6qlt52zj@treble> (raw)
In-Reply-To: <201708171831.UZFoxEFx%fengguang.wu@intel.com>
On Thu, Aug 17, 2017 at 06:33:35PM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/core
> head: 52fa5bc5cbba089f09bc2c372e3432f3f3e48051
> commit: 7a46ec0e2f4850407de5e1d19a44edee6efa58ec [36/40] locking/refcounts, x86/asm: Implement fast refcount overflow protection
> config: i386-tinyconfig (attached as .config)
> compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
> reproduce:
> git checkout 7a46ec0e2f4850407de5e1d19a44edee6efa58ec
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All error/warnings (new ones prefixed by >>):
>
> In file included from include/linux/refcount.h:57:0,
> from include/linux/kref.h:19,
> from include/linux/kobject.h:24,
> from include/linux/irqdesc.h:5,
> from include/linux/irq.h:495,
> from arch/x86/include/asm/hardirq.h:5,
> from include/linux/hardirq.h:8,
> from arch/x86/kernel/asm-offsets.c:11:
> arch/x86/include/asm/refcount.h: In function 'refcount_add':
> >> arch/x86/include/asm/refcount.h:21:2: error: expected ':' or ')' before 'ASM_UNREACHABLE'
This needs the ASM_UNREACHABLE macro from the tip/x86/asm branch.
--
Josh
prev parent reply other threads:[~2017-08-17 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 10:33 kbuild test robot
2017-08-17 12:55 ` Josh Poimboeuf [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=20170817125553.hhw2nbft6qlt52zj@treble \
--to=jpoimboe@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tipbuild@zytor.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
all inboxes | Powered by JetHome®