mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: [rcu:dev.2020.03.16a 60/68] kernel/rcu/tasks.h:1000:37: error: 'rcu_tasks_rude' undeclared; did you mean 'rcu_tasks_qs'?
Date: Tue, 17 Mar 2020 15:25:45 -0700	[thread overview]
Message-ID: <20200317222545.GO3199@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <202003180521.jou9H4n6%lkp@intel.com>

On Wed, Mar 18, 2020 at 05:28:25AM +0800, kbuild test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2020.03.16a
> head:   ad7a7c12b09555e7c488ee3be512d549cd78a2c0
> commit: 277258c315b7c732948e47718de02c6908d1745e [60/68] rcu-tasks: Add RCU tasks to rcutorture writer stall output
> config: arc-defconfig (attached as .config)
> compiler: arc-elf-gcc (GCC) 9.2.0
> reproduce:
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         git checkout 277258c315b7c732948e47718de02c6908d1745e
>         # save the attached .config to linux build tree
>         GCC_VERSION=9.2.0 make.cross ARCH=arc 
> 
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>):
> 
>    In file included from kernel/rcu/update.c:562:
>    kernel/rcu/tasks.h: In function 'show_rcu_tasks_gp_kthreads':
> >> kernel/rcu/tasks.h:1000:37: error: 'rcu_tasks_rude' undeclared (first use in this function); did you mean 'rcu_tasks_qs'?
>     1000 |  show_rcu_tasks_generic_gp_kthread(&rcu_tasks_rude, "");
>          |                                     ^~~~~~~~~~~~~~
>          |                                     rcu_tasks_qs
>    kernel/rcu/tasks.h:1000:37: note: each undeclared identifier is reported only once for each function it appears in

Good catch!  Will fix!!!

							Thanx, Paul

> vim +1000 kernel/rcu/tasks.h
> 
>    996	
>    997	void show_rcu_tasks_gp_kthreads(void)
>    998	{
>    999		show_rcu_tasks_generic_gp_kthread(&rcu_tasks, "");
> > 1000		show_rcu_tasks_generic_gp_kthread(&rcu_tasks_rude, "");
>   1001		show_rcu_tasks_trace_gp_kthread();
>   1002	}
>   1003	
> 
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org



      reply	other threads:[~2020-03-17 22:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-17 21:28 kbuild test robot
2020-03-17 22:25 ` Paul E. McKenney [this message]

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=20200317222545.GO3199@paulmck-ThinkPad-P72 \
    --to=paulmck@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@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®