linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: [rcu:peterz.2019.05.09a 2/5] ERROR: "tracing_stop" [kernel/rcu/rcutorture.ko] undefined!
Date: Thu, 9 May 2019 15:18:57 -0700	[thread overview]
Message-ID: <20190509221857.GN3923@linux.ibm.com> (raw)
In-Reply-To: <201905100531.n2nODfWZ%lkp@intel.com>

On Fri, May 10, 2019 at 05:47:32AM +0800, kbuild test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git peterz.2019.05.09a
> head:   9aaf2ab4ea3d421a1efa413020bbd5c30ecb5f86
> commit: 88437e0ce11d4b74d9606e2c587cdebbdfb41cf3 [2/5] EXP rcutorture: Test setup for sched_setaffinity()
> config: x86_64-lkp (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
> reproduce:
>         git checkout 88437e0ce11d4b74d9606e2c587cdebbdfb41cf3
>         # save the attached .config to linux build tree
>         make ARCH=x86_64 
> 
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>):
> 
> >> ERROR: "tracing_stop" [kernel/rcu/rcutorture.ko] undefined!

Apologies, this is an experimental commit not intended for mainline.
So it only works when rcutorture is built in.

							Thanx, Paul


      reply	other threads:[~2019-05-09 22:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09 21:47 [rcu:peterz.2019.05.09a 2/5] ERROR: "tracing_stop" [kernel/rcu/rcutorture.ko] undefined! kbuild test robot
2019-05-09 22:18 ` 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=20190509221857.GN3923@linux.ibm.com \
    --to=paulmck@linux.ibm.com \
    --cc=kbuild-all@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;
as well as URLs for NNTP newsgroup(s).