From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Apr 19 (waketorture.c)
Date: Tue, 19 Apr 2016 13:01:44 -0700 [thread overview]
Message-ID: <20160419200144.GA12164@linux.vnet.ibm.com> (raw)
In-Reply-To: <57168832.9020400@infradead.org>
On Tue, Apr 19, 2016 at 12:34:10PM -0700, Randy Dunlap wrote:
> On 04/19/16 12:05, Paul E. McKenney wrote:
> > On Tue, Apr 19, 2016 at 10:55:21AM -0700, Randy Dunlap wrote:
> >> On 04/19/16 09:56, Paul E. McKenney wrote:
> >>> On Tue, Apr 19, 2016 at 09:20:24AM -0700, Randy Dunlap wrote:
> >>>> On 04/18/16 22:13, Stephen Rothwell wrote:
> >>>>> Hi all,
> >>>>>
> >>>>> Changes since 20160418:
> >>>>>
> >>>>
> >>>> on x86_64:
> >>>>
> >>>> kernel/built-in.o: In function `wake_torture_stats_print':
> >>>> waketorture.c:(.text+0x2f06d): undefined reference to `trace_clock_global'
> >>>> kernel/built-in.o: In function `wake_torture_waiter':
> >>>> waketorture.c:(.text+0x2f196): undefined reference to `trace_clock_local'
> >>>> waketorture.c:(.text+0x2f1bc): undefined reference to `trace_clock_local'
> >>>> waketorture.c:(.text+0x2f1d4): undefined reference to `trace_clock_local'
> >>>> waketorture.c:(.text+0x2f237): undefined reference to `trace_clock_local'
> >>>> waketorture.c:(.text+0x2f253): undefined reference to `trace_clock_local'
> >>>> kernel/built-in.o:waketorture.c:(.text+0x2f318): more undefined references to `trace_clock_local' follow
> >>>> kernel/built-in.o: In function `wake_torture_init':
> >>>> waketorture.c:(.init.text+0x2b3f): undefined reference to `trace_clock_global'
> >>>>
> >>>>
> >>>> Full randconfig file is attached.
> >>>
> >>> I don't see the .config, could you please send it to me?
> >>>
> >>> Looks like I need to add a few "depends" or "selects" clauses...
> >>
> >> Weird, mail client told me that it was attaching the config file.
> >> Trying again...
> >
> > I know that feeling!
> >
> > Does the following patch help? (The 64BIT is unrelated, feel free
> > to back that part out if you wish.)
>
> Yes, that works for me. Thanks.
>
> Acked-by: Randy Dunlap <rdunlap@infradead.org>
Very good, thank you!
Thanx, Paul
> > ------------------------------------------------------------------------
> >
> > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> > index 8644658e75c0..a42570a0fb56 100644
> > --- a/lib/Kconfig.debug
> > +++ b/lib/Kconfig.debug
> > @@ -1434,7 +1434,8 @@ config RCU_TORTURE_TEST_SLOW_CLEANUP_DELAY
> > config WAKE_TORTURE_TEST
> > tristate "Torture test for wakeups and CPU hotplug"
> > depends on DEBUG_KERNEL
> > - depends on X86_64 || ARM64 || PPC64 || MIPS
> > + depends on 64BIT
> > + depends on TRACE_CLOCK
> > select TORTURE_TEST
> > default n
> > help
> >
>
>
>
> --
> ~Randy
>
prev parent reply other threads:[~2016-04-19 20:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 5:13 linux-next: Tree for Apr 19 Stephen Rothwell
2016-04-19 16:20 ` linux-next: Tree for Apr 19 (waketorture.c) Randy Dunlap
2016-04-19 16:56 ` Paul E. McKenney
2016-04-19 17:55 ` Randy Dunlap
2016-04-19 19:05 ` Paul E. McKenney
2016-04-19 19:34 ` Randy Dunlap
2016-04-19 20:01 ` 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=20160419200144.GA12164@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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.