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 Mar 30 (waketorture.c)
Date: Wed, 30 Mar 2016 10:03:19 -0700 [thread overview]
Message-ID: <20160330170319.GK4287@linux.vnet.ibm.com> (raw)
In-Reply-To: <56FC054F.8010706@infradead.org>
On Wed, Mar 30, 2016 at 09:56:47AM -0700, Randy Dunlap wrote:
> On 03/29/16 18:50, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20160329:
> >
>
>
> on i386 or x86_64:
>
> waketorture.c:(.text+0x5d578): undefined reference to `trace_clock_global'
> waketorture.c:(.text+0x5d731): undefined reference to `trace_clock_local'
> waketorture.c:(.text+0x5d765): undefined reference to `trace_clock_local'
> waketorture.c:(.text+0x5d7a7): undefined reference to `trace_clock_local'
> waketorture.c:(.text+0x5d835): undefined reference to `trace_clock_local'
> waketorture.c:(.text+0x5d879): undefined reference to `trace_clock_local'
> kernel/built-in.o:waketorture.c:(.text+0x5d9a3): more undefined references to `trace_clock_local' follow
> waketorture.c:(.init.text+0x3e11): undefined reference to `trace_clock_global'
>
>
> on i386:
>
> kernel/built-in.o: In function `wake_torture_stats_print':
> waketorture.c:(.text+0x4a990): undefined reference to `__udivdi3'
> waketorture.c:(.text+0x4a9eb): undefined reference to `__udivdi3'
> waketorture.c:(.text+0x4a9fd): undefined reference to `__udivdi3'
> waketorture.c:(.text+0x4aa19): undefined reference to `__umoddi3'
> waketorture.c:(.text+0x4aa39): undefined reference to `__udivdi3'
>
>
>
> Let me know if you need .config files for any of these.
My mistake pushing a diagnostic commit to -next. I have updated to
avoid doing so.
Thanx, Paul
next prev parent reply other threads:[~2016-03-30 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 1:50 linux-next: Tree for Mar 30 Stephen Rothwell
2016-03-30 16:56 ` linux-next: Tree for Mar 30 (waketorture.c) Randy Dunlap
2016-03-30 17:03 ` Paul E. McKenney [this message]
2016-03-30 17:13 ` linux-next: Tree for Mar 30 (lockdep.c) Randy Dunlap
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=20160330170319.GK4287@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 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).