From: kbuild test robot <lkp@intel.com>
To: Jeffrey Merkey <jeffmerkey@gmail.com>
Cc: kbuild-all@01.org, hpa@zytor.com, jeffmerkey@gmail.com,
linux-kernel@vger.kernel.org, mingo@redhat.com,
tglx@linutronix.de, x86@kernel.org
Subject: Re: [PATCH 1/4] Add BUG_XX() debugging options
Date: Tue, 2 Feb 2016 04:27:06 +0800 [thread overview]
Message-ID: <201602020408.AimXA0CS%fengguang.wu@intel.com> (raw)
In-Reply-To: <1454356886-12334-1-git-send-email-jeffmerkey@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2125 bytes --]
Hi Jeffrey,
[auto build test WARNING on v4.5-rc2]
[also build test WARNING on next-20160201]
[cannot apply to tip/x86/core]
[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/Jeffrey-Merkey/Add-BUG_XX-debugging-options/20160202-040506
config: x86_64-randconfig-x012-201605 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
In file included from include/linux/bug.h:4:0,
from include/linux/page-flags.h:9,
from kernel/bounds.c:9:
>> arch/x86/include/asm/bug.h:14:5: warning: "CONFIG_DEBUG_BUG" is not defined [-Wundef]
#if CONFIG_DEBUG_BUG
^
--
In file included from include/linux/bug.h:4:0,
from include/linux/page-flags.h:9,
from kernel/bounds.c:9:
>> arch/x86/include/asm/bug.h:14:5: warning: "CONFIG_DEBUG_BUG" is not defined [-Wundef]
#if CONFIG_DEBUG_BUG
^
In file included from include/linux/bug.h:4:0,
from include/linux/crypto.h:23,
from arch/x86/kernel/asm-offsets.c:8:
>> arch/x86/include/asm/bug.h:14:5: warning: "CONFIG_DEBUG_BUG" is not defined [-Wundef]
#if CONFIG_DEBUG_BUG
^
vim +/CONFIG_DEBUG_BUG +14 arch/x86/include/asm/bug.h
1 #ifndef _ASM_X86_BUG_H
2 #define _ASM_X86_BUG_H
3
4 #define HAVE_ARCH_BUG
5
6 #ifdef CONFIG_DEBUG_BUGVERBOSE
7
8 #ifdef CONFIG_X86_32
9 # define __BUG_C0 "2:\t.long 1b, %c0\n"
10 #else
11 # define __BUG_C0 "2:\t.long 1b - 2b, %c0 - 2b\n"
12 #endif
13
> 14 #if CONFIG_DEBUG_BUG
15 #define BUG() \
16 do { \
17 asm volatile("int3"); \
18 unreachable(); \
19 } while (0)
20 #else
21 #define BUG() \
22 do { \
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 20303 bytes --]
next prev parent reply other threads:[~2016-02-01 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 20:01 Jeffrey Merkey
2016-02-01 20:27 ` kbuild test robot [this message]
2016-02-01 20:33 ` Jeffrey Merkey
2016-02-01 20:36 ` Jeffrey Merkey
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=201602020408.AimXA0CS%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=hpa@zytor.com \
--cc=jeffmerkey@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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®