From: Andrew Morton <akpm@linux-foundation.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
avi@redhat.com, Marcelo Tosatti <mtosatti@redhat.com>,
Alexander Graf <agraf@suse.de>
Subject: Re: linux-next: Tree for January 23 (kvm)
Date: Wed, 28 Jan 2009 01:51:49 -0800 [thread overview]
Message-ID: <20090128015149.791e10dd.akpm@linux-foundation.org> (raw)
In-Reply-To: <497A29D0.2010307@oracle.com>
On Fri, 23 Jan 2009 12:34:24 -0800 Randy Dunlap <randy.dunlap@oracle.com> wrote:
> Stephen Rothwell wrote:
> > Hi all,
> >
> > News: I will be on leave next week, so there will probably be no
> > linux-next release until Feb 2.
> >
> > Changes since 20090122:
>
>
> kvm changes cause this build error on i386:
>
> when kvm is built as module:
> ERROR: "__moddi3" [arch/x86/kvm/kvm.ko] undefined!
>
> or when kvm is built into the kernel image:
> lapic.c:(.text+0x19276): undefined reference to `__moddi3'
>
>
> I guess it's this line:
> ns = ktime_to_ns(remaining) % apic->timer.period;
>
dammit, I just spent N minutes hunting down the same thing in
the Jan 26 linux-next :(
next prev parent reply other threads:[~2009-01-28 9:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 7:48 linux-next: Tree for January 23 Stephen Rothwell
2009-01-23 20:34 ` linux-next: Tree for January 23 (kvm) Randy Dunlap
2009-01-28 9:51 ` Andrew Morton [this message]
2009-01-28 10:20 ` Alexander Graf
2009-02-04 13:55 ` Avi Kivity
2009-01-23 21:03 ` [PATCH] kmemtrace: fix printk format warnings Randy Dunlap
2009-01-23 21:21 ` linux-next: Tree for January 23 (drivers/watchdog/cpwd.c:411: error: 'inode' undeclared (first use in this function)) Alexey Dobriyan
2009-01-23 21:46 ` linux-next: Tree for January 23 (9pnet_rdma) Richard Holden
2009-01-23 23:00 ` [patch -next] 9pnet_rdma build error 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=20090128015149.791e10dd.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=randy.dunlap@oracle.com \
--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).