From: kernel test robot <lkp@intel.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: [rt-devel:linux-5.18.y-rt-rebase 17/78] kernel/printk/printk.c:3182:13: warning: function 'console_emit_next_record' has internal linkage but is not defined
Date: Fri, 22 Apr 2022 17:48:11 +0800 [thread overview]
Message-ID: <202204221737.XUqb9giP-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git linux-5.18.y-rt-rebase
head: 03e7725ddbfb0ffd7f3d7b257bfa504c6f795f6b
commit: 72b5c1227b73b2cde1452cfc58717cff442ed473 [17/78] serial: 8250: implement write_atomic
config: hexagon-randconfig-r002-20220422 (https://download.01.org/0day-ci/archive/20220422/202204221737.XUqb9giP-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 5bd87350a5ae429baf8f373cb226a57b62f87280)
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/rt/linux-rt-devel.git/commit/?id=72b5c1227b73b2cde1452cfc58717cff442ed473
git remote add rt-devel https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git
git fetch --no-tags rt-devel linux-5.18.y-rt-rebase
git checkout 72b5c1227b73b2cde1452cfc58717cff442ed473
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash kernel/printk/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
kernel/printk/printk.c:3187:7: warning: variable 'any_usable' set but not used [-Wunused-but-set-variable]
bool any_usable = false;
^
>> kernel/printk/printk.c:3182:13: warning: function 'console_emit_next_record' has internal linkage but is not defined [-Wundefined-internal]
static bool console_emit_next_record(struct console *con, char *text, char *ext_text,
^
kernel/printk/printk.c:3215:16: note: used here
progress = console_emit_next_record(con,
^
2 warnings generated.
vim +/console_emit_next_record +3182 kernel/printk/printk.c
fe3d8ad31cf51b kernel/printk.c Feng Tang 2011-03-22 3180
943b66638a0519 kernel/printk/printk.c John Ogness 2022-02-04 3181 #ifdef CONFIG_HAVE_ATOMIC_CONSOLE
943b66638a0519 kernel/printk/printk.c John Ogness 2022-02-04 @3182 static bool console_emit_next_record(struct console *con, char *text, char *ext_text,
943b66638a0519 kernel/printk/printk.c John Ogness 2022-02-04 3183 char *dropped_text, bool atomic_printing);
943b66638a0519 kernel/printk/printk.c John Ogness 2022-02-04 3184
:::::: The code at line 3182 was first introduced by commit
:::::: 943b66638a0519612cdc25dcb07f59af89d37407 printk: add infrastucture for atomic consoles
:::::: TO: John Ogness <john.ogness@linutronix.de>
:::::: CC: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-04-22 9:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202204221737.XUqb9giP-lkp@intel.com \
--to=lkp@intel.com \
--cc=bigeasy@linutronix.de \
--cc=john.ogness@linutronix.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).