From: kernel test robot <lkp@intel.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [jirislaby:devel 41/62] include/asm-generic/bug.h:68:3: error: implicit declaration of function 'printk'; did you mean '_printk'?
Date: Thu, 22 Jul 2021 07:27:19 +0800 [thread overview]
Message-ID: <202107220711.7927SIx6-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3638 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux.git devel
head: fb40a2c5242ac12784ec96caeede97082e3c1813
commit: a19a6a12ffba0cf0e400e6abefd49a87b119ff4a [41/62] include condition in the BUG_ON/WARN_ON output
config: arm64-allyesconfig (attached as .config)
compiler: aarch64-linux-gcc (GCC) 10.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux.git/commit/?id=a19a6a12ffba0cf0e400e6abefd49a87b119ff4a
git remote add jirislaby https://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux.git
git fetch --no-tags jirislaby devel
git checkout a19a6a12ffba0cf0e400e6abefd49a87b119ff4a
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from arch/arm64/include/asm/bug.h:26,
from include/linux/bug.h:5,
from include/linux/cpumask.h:14,
from include/linux/smp.h:13,
from include/linux/lockdep.h:14,
from include/linux/mutex.h:17,
from include/linux/kernfs.h:12,
from include/linux/sysfs.h:16,
from include/linux/kobject.h:20,
from include/linux/of.h:17,
from include/linux/irqdomain.h:35,
from include/linux/acpi.h:13,
from arch/arm64/kernel/setup.c:9:
arch/arm64/kernel/setup.c: In function 'dump_kernel_offset':
>> include/asm-generic/bug.h:68:3: error: implicit declaration of function 'printk'; did you mean '_printk'? [-Werror=implicit-function-declaration]
68 | printk("BUG: '%s' is true!\n", __stringify(condition)); \
| ^~~~~~
include/linux/mmdebug.h:17:25: note: in expansion of macro 'BUG_ON'
17 | #define VM_BUG_ON(cond) BUG_ON(cond)
| ^~~~~~
arch/arm64/include/asm/memory.h:184:25: note: in expansion of macro 'VM_BUG_ON'
184 | #define PHYS_OFFSET ({ VM_BUG_ON(memstart_addr & 1); memstart_addr; })
| ^~~~~~~~~
include/linux/printk.h:430:19: note: in expansion of macro 'PHYS_OFFSET'
430 | _p_func(_fmt, ##__VA_ARGS__); \
| ^~~~~~~~~~~
include/linux/printk.h:434:26: note: in expansion of macro 'printk_index_wrap'
434 | #define printk(fmt, ...) printk_index_wrap(_printk, fmt, ##__VA_ARGS__)
| ^~~~~~~~~~~~~~~~~
include/linux/printk.h:447:2: note: in expansion of macro 'printk'
447 | printk(KERN_EMERG pr_fmt(fmt), ##__VA_ARGS__)
| ^~~~~~
arch/arm64/kernel/setup.c:422:3: note: in expansion of macro 'pr_emerg'
422 | pr_emerg("PHYS_OFFSET: 0x%llx\n", PHYS_OFFSET);
| ^~~~~~~~
cc1: some warnings being treated as errors
vim +68 include/asm-generic/bug.h
64
65 #ifndef HAVE_ARCH_BUG_ON
66 #define BUG_ON(condition) do { \
67 if (unlikely(condition)) { \
> 68 printk("BUG: '%s' is true!\n", __stringify(condition)); \
69 BUG(); \
70 } \
71 } while(0)
72 #endif
73
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 78226 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [jirislaby:devel 41/62] include/asm-generic/bug.h:68:3: error: implicit declaration of function 'printk'; did you mean '_printk'?
Date: Thu, 22 Jul 2021 07:27:19 +0800 [thread overview]
Message-ID: <202107220711.7927SIx6-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3714 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux.git devel
head: fb40a2c5242ac12784ec96caeede97082e3c1813
commit: a19a6a12ffba0cf0e400e6abefd49a87b119ff4a [41/62] include condition in the BUG_ON/WARN_ON output
config: arm64-allyesconfig (attached as .config)
compiler: aarch64-linux-gcc (GCC) 10.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux.git/commit/?id=a19a6a12ffba0cf0e400e6abefd49a87b119ff4a
git remote add jirislaby https://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux.git
git fetch --no-tags jirislaby devel
git checkout a19a6a12ffba0cf0e400e6abefd49a87b119ff4a
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from arch/arm64/include/asm/bug.h:26,
from include/linux/bug.h:5,
from include/linux/cpumask.h:14,
from include/linux/smp.h:13,
from include/linux/lockdep.h:14,
from include/linux/mutex.h:17,
from include/linux/kernfs.h:12,
from include/linux/sysfs.h:16,
from include/linux/kobject.h:20,
from include/linux/of.h:17,
from include/linux/irqdomain.h:35,
from include/linux/acpi.h:13,
from arch/arm64/kernel/setup.c:9:
arch/arm64/kernel/setup.c: In function 'dump_kernel_offset':
>> include/asm-generic/bug.h:68:3: error: implicit declaration of function 'printk'; did you mean '_printk'? [-Werror=implicit-function-declaration]
68 | printk("BUG: '%s' is true!\n", __stringify(condition)); \
| ^~~~~~
include/linux/mmdebug.h:17:25: note: in expansion of macro 'BUG_ON'
17 | #define VM_BUG_ON(cond) BUG_ON(cond)
| ^~~~~~
arch/arm64/include/asm/memory.h:184:25: note: in expansion of macro 'VM_BUG_ON'
184 | #define PHYS_OFFSET ({ VM_BUG_ON(memstart_addr & 1); memstart_addr; })
| ^~~~~~~~~
include/linux/printk.h:430:19: note: in expansion of macro 'PHYS_OFFSET'
430 | _p_func(_fmt, ##__VA_ARGS__); \
| ^~~~~~~~~~~
include/linux/printk.h:434:26: note: in expansion of macro 'printk_index_wrap'
434 | #define printk(fmt, ...) printk_index_wrap(_printk, fmt, ##__VA_ARGS__)
| ^~~~~~~~~~~~~~~~~
include/linux/printk.h:447:2: note: in expansion of macro 'printk'
447 | printk(KERN_EMERG pr_fmt(fmt), ##__VA_ARGS__)
| ^~~~~~
arch/arm64/kernel/setup.c:422:3: note: in expansion of macro 'pr_emerg'
422 | pr_emerg("PHYS_OFFSET: 0x%llx\n", PHYS_OFFSET);
| ^~~~~~~~
cc1: some warnings being treated as errors
vim +68 include/asm-generic/bug.h
64
65 #ifndef HAVE_ARCH_BUG_ON
66 #define BUG_ON(condition) do { \
67 if (unlikely(condition)) { \
> 68 printk("BUG: '%s' is true!\n", __stringify(condition)); \
69 BUG(); \
70 } \
71 } while(0)
72 #endif
73
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 78226 bytes --]
next reply other threads:[~2021-07-21 23:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 23:27 kernel test robot [this message]
2021-07-21 23:27 ` [jirislaby:devel 41/62] include/asm-generic/bug.h:68:3: error: implicit declaration of function 'printk'; did you mean '_printk'? kernel test robot
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=202107220711.7927SIx6-lkp@intel.com \
--to=lkp@intel.com \
--cc=jslaby@suse.cz \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.