All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [rt-devel:linux-6.3.y-rt 4/5] kernel/printk/printk.c:3365:6: warning: no previous prototype for 'console_bkl_kthread_create'
Date: Fri, 24 Mar 2023 17:03:58 +0800	[thread overview]
Message-ID: <202303241710.83IbYO2x-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git linux-6.3.y-rt
head:   93adb32305897d3e6cb5b333fb8873ecff8c68fe
commit: b111e33ae076e9a8cdedb202d0391d23ed420e96 [4/5] printk: Update John's printk series.
config: csky-randconfig-r025-20230322 (https://download.01.org/0day-ci/archive/20230324/202303241710.83IbYO2x-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 12.1.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/rt/linux-rt-devel.git/commit/?id=b111e33ae076e9a8cdedb202d0391d23ed420e96
        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-6.3.y-rt
        git checkout b111e33ae076e9a8cdedb202d0391d23ed420e96
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=csky olddefconfig
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=csky SHELL=/bin/bash kernel/printk/

If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202303241710.83IbYO2x-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> kernel/printk/printk.c:3365:6: warning: no previous prototype for 'console_bkl_kthread_create' [-Wmissing-prototypes]
    3365 | void console_bkl_kthread_create(void)
         |      ^~~~~~~~~~~~~~~~~~~~~~~~~~


vim +/console_bkl_kthread_create +3365 kernel/printk/printk.c

  3364	
> 3365	void console_bkl_kthread_create(void)
  3366	{
  3367		struct task_struct *kt;
  3368		struct console *c;
  3369	
  3370		lockdep_assert_held(&console_mutex);
  3371	
  3372		if (!IS_ENABLED(CONFIG_PREEMPT_RT))
  3373			return;
  3374	
  3375		if (!printk_threads_enabled || console_bkl_kthread)
  3376			return;
  3377	
  3378		for_each_console(c) {
  3379			if (c->flags & CON_BOOT)
  3380				return;
  3381		}
  3382	
  3383		kt = kthread_run(console_bkl_kthread_func, NULL, "pr/bkl");
  3384		if (IS_ERR(kt)) {
  3385			pr_err("unable to start BKL printing thread\n");
  3386			return;
  3387		}
  3388	
  3389		console_bkl_kthread = kt;
  3390	
  3391		/*
  3392		 * It is important that console printing threads are scheduled
  3393		 * shortly after a printk call and with generous runtime budgets.
  3394		 */
  3395		sched_set_normal(console_bkl_kthread, -20);
  3396	}
  3397	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests

                 reply	other threads:[~2023-03-24  9:04 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=202303241710.83IbYO2x-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bigeasy@linutronix.de \
    --cc=oe-kbuild-all@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 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.