From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Sreenath Vijayan <sreenath.vijayan@sony.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-serial@vger.kernel.org,
Shimoyashiki Taichi <taichi.shimoyashiki@sony.com>,
John Ogness <john.ogness@linutronix.de>
Subject: Re: [tty:tty-testing 28/29] include/linux/printk.h:275:13: error: unused function 'dump_printk_buffer'
Date: Wed, 7 Feb 2024 09:51:42 +0000 [thread overview]
Message-ID: <2024020708-unknotted-ceramics-f6ec@gregkh> (raw)
In-Reply-To: <202402071252.Zj78sTXN-lkp@intel.com>
On Wed, Feb 07, 2024 at 12:22:40PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
> head: 014e10bea593b963574d607faa34e7eaaad3c02b
> commit: 558367b641b3802572132e7ed865f5eb887c41ea [28/29] printk: Add function to dump printk buffer directly to consoles
> config: i386-buildonly-randconfig-006-20240207 (https://download.01.org/0day-ci/archive/20240207/202402071252.Zj78sTXN-lkp@intel.com/config)
> compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240207/202402071252.Zj78sTXN-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202402071252.Zj78sTXN-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> In file included from lib/test_bitops.c:9:
> In file included from include/linux/module.h:13:
> In file included from include/linux/stat.h:19:
> In file included from include/linux/time.h:60:
> In file included from include/linux/time32.h:13:
> In file included from include/linux/timex.h:67:
> In file included from arch/x86/include/asm/timex.h:5:
> In file included from arch/x86/include/asm/processor.h:23:
> In file included from arch/x86/include/asm/msr.h:11:
> In file included from arch/x86/include/asm/cpumask.h:5:
> In file included from include/linux/cpumask.h:10:
> In file included from include/linux/kernel.h:31:
> >> include/linux/printk.h:275:13: error: unused function 'dump_printk_buffer' [-Werror,-Wunused-function]
> 275 | static void dump_printk_buffer(void)
> | ^~~~~~~~~~~~~~~~~~
> 1 error generated.
>
>
> vim +/dump_printk_buffer +275 include/linux/printk.h
>
> 268
> 269 static inline void dump_stack(void)
> 270 {
> 271 }
> 272 static inline void printk_trigger_flush(void)
> 273 {
> 274 }
> > 275 static void dump_printk_buffer(void)
Ah, inline was missed :(
I'll drop these from my tree for now, can you resubmit fixed patches
with all of the collected reviewed tags?
thanks,
greg k-h
next prev parent reply other threads:[~2024-02-07 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 4:22 [tty:tty-testing 28/29] include/linux/printk.h:275:13: error: unused function 'dump_printk_buffer' kernel test robot
2024-02-07 9:51 ` Greg Kroah-Hartman [this message]
2024-02-07 10:27 ` Sreenath Vijayan
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=2024020708-unknotted-ceramics-f6ec@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=john.ogness@linutronix.de \
--cc=linux-serial@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sreenath.vijayan@sony.com \
--cc=taichi.shimoyashiki@sony.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