From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: [rcu:rcu/dev 24/25] ERROR: "schedule_timeout_set_task2dump" [kernel/torture.ko] undefined!
Date: Wed, 6 Dec 2017 14:08:58 -0800 [thread overview]
Message-ID: <20171206220858.GD7829@linux.vnet.ibm.com> (raw)
In-Reply-To: <201712070631.KQ3P1R3S%fengguang.wu@intel.com>
On Thu, Dec 07, 2017 at 06:03:12AM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/dev
> head: dab0b22dfc3bd3ed37876b2465dc622a39ae25e0
> commit: aa2b802cb432a725589884d2ba47833de21e0871 [24/25] EXP: timer: Dump __cpuhp_kick_ap task state
> config: x86_64-kexec (attached as .config)
> compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025
> reproduce:
> git checkout aa2b802cb432a725589884d2ba47833de21e0871
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All errors (new ones prefixed by >>):
>
> >> ERROR: "schedule_timeout_set_task2dump" [kernel/torture.ko] undefined!
This is experimental code which will be reworked before hitting mainline.
Apologies for the noise!
Thanx, Paul
next prev parent reply other threads:[~2017-12-06 22:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 22:03 [rcu:rcu/dev 24/25] ERROR: "schedule_timeout_set_task2dump" [kernel/torture.ko] undefined! kbuild test robot
2017-12-06 22:08 ` Paul E. McKenney [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-07 5:57 kbuild test robot
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=20171206220858.GD7829@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
/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.