From: kbuild test robot <lkp@intel.com>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: kbuild-all@01.org, Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH] ia64: tweak BREAK_LOGLEVEL and RESTORE_LOGLEVEL
Date: Mon, 7 Jan 2019 21:26:14 +0800 [thread overview]
Message-ID: <201901072128.HGGbw9UZ%fengguang.wu@intel.com> (raw)
In-Reply-To: <20190107095433.6497-1-sergey.senozhatsky@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3101 bytes --]
Hi Sergey,
I love your patch! Yet something to improve:
[auto build test ERROR on ia64/next]
[also build test ERROR on v5.0-rc1]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Sergey-Senozhatsky/ia64-tweak-BREAK_LOGLEVEL-and-RESTORE_LOGLEVEL/20190107-191240
base: https://git.kernel.org/pub/scm/linux/kernel/git/aegl/linux.git next
config: ia64-allmodconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 8.1.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=8.1.0 make.cross ARCH=ia64
All errors (new ones prefixed by >>):
arch/ia64/kernel/mca.c: In function 'ia64_mlogbuf_finish':
>> arch/ia64/kernel/mca.c:195:20: error: '__console_loglevel' undeclared (first use in this function); did you mean 'console_loglevel'?
loglevel_save = __console_loglevel; \
^~~~~~~~~~~~~~~~~~
arch/ia64/kernel/mca.c:294:2: note: in expansion of macro 'BREAK_LOGLEVEL'
BREAK_LOGLEVEL();
^~~~~~~~~~~~~~
arch/ia64/kernel/mca.c:195:20: note: each undeclared identifier is reported only once for each function it appears in
loglevel_save = __console_loglevel; \
^~~~~~~~~~~~~~~~~~
arch/ia64/kernel/mca.c:294:2: note: in expansion of macro 'BREAK_LOGLEVEL'
BREAK_LOGLEVEL();
^~~~~~~~~~~~~~
arch/ia64/kernel/mca.c: In function 'default_monarch_init_process':
>> arch/ia64/kernel/mca.c:195:20: error: '__console_loglevel' undeclared (first use in this function); did you mean 'console_loglevel'?
loglevel_save = __console_loglevel; \
^~~~~~~~~~~~~~~~~~
arch/ia64/kernel/mca.c:1623:2: note: in expansion of macro 'BREAK_LOGLEVEL'
BREAK_LOGLEVEL();
^~~~~~~~~~~~~~
vim +195 arch/ia64/kernel/mca.c
43ed3baf Hidetoshi Seto 2006-09-26 189
43ed3baf Hidetoshi Seto 2006-09-26 190 static int loglevel_save = -1;
5a53b9d7 Sergey Senozhatsky 2019-01-07 191 #define BREAK_LOGLEVEL() \
5a53b9d7 Sergey Senozhatsky 2019-01-07 192 do { \
5a53b9d7 Sergey Senozhatsky 2019-01-07 193 bust_spinlocks(1); \
43ed3baf Hidetoshi Seto 2006-09-26 194 if (loglevel_save < 0) \
43ed3baf Hidetoshi Seto 2006-09-26 @195 loglevel_save = __console_loglevel; \
5a53b9d7 Sergey Senozhatsky 2019-01-07 196 console_loglevel = CONSOLE_LOGLEVEL_MOTORMOUTH; \
5a53b9d7 Sergey Senozhatsky 2019-01-07 197 } while (0)
43ed3baf Hidetoshi Seto 2006-09-26 198
:::::: The code at line 195 was first introduced by commit
:::::: 43ed3baf623410b3fa6ca14a9d3f6deca3493c56 [IA64] printing support for MCA/INIT
:::::: TO: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
:::::: CC: Tony Luck <tony.luck@intel.com>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 52363 bytes --]
next prev parent reply other threads:[~2019-01-07 13:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 9:54 Sergey Senozhatsky
2019-01-07 13:26 ` kbuild test robot [this message]
2019-01-07 14:48 ` Sergey Senozhatsky
2019-01-07 14:52 ` [PATCHv2] " Sergey Senozhatsky
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=201901072128.HGGbw9UZ%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=fenghua.yu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=tony.luck@intel.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®