From: Randy Dunlap <randy.dunlap@oracle.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
kvm@vger.kernel.org, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for November 22 (kvm)
Date: Mon, 29 Nov 2010 08:33:24 -0800 [thread overview]
Message-ID: <20101129083324.6870d7da.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20101122132627.bd4e88ef.randy.dunlap@oracle.com>
On Mon, 22 Nov 2010 13:26:27 -0800 Randy Dunlap wrote:
> On Mon, 22 Nov 2010 13:49:11 +1100 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20101119:
>
>
> kvm.c:(.init.text+0x11f49): undefined reference to `kvm_register_clock'
>
> when CONFIG_KVM_CLOCK is not enabled.
BUild error still present in linux-next-2010-NOV-29.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-11-29 16:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 2:49 linux-next: Tree for November 22 Stephen Rothwell
2010-11-22 12:47 ` Zimny Lech
[not found] ` <20101122134911.b7e106f9.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2010-11-22 15:37 ` Zimny Lech
2010-11-22 15:37 ` Zimny Lech
2010-11-22 19:46 ` Greg KH
[not found] ` <20101122194643.GB21985-l3A5Bk7waGM@public.gmane.org>
2010-11-22 20:08 ` Arend Van Spriel
2010-11-22 20:08 ` Arend Van Spriel
2010-11-22 21:31 ` Greg KH
2010-11-22 19:55 ` Zimny Lech
2010-11-22 21:26 ` linux-next: Tree for November 22 (kvm) Randy Dunlap
2010-11-29 16:33 ` Randy Dunlap [this message]
2010-11-29 16:35 ` Avi Kivity
2010-11-29 17:47 ` Zachary Amsden
2010-11-29 17:52 ` Randy Dunlap
2010-11-29 18:08 ` Zachary Amsden
2010-11-29 19:05 ` Randy Dunlap
2010-11-30 12:17 ` Glauber Costa
2010-11-30 18:09 ` Zachary Amsden
2010-12-10 17:18 ` Randy Dunlap
2010-12-12 9:23 ` Avi Kivity
2010-12-16 9:37 ` Avi Kivity
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=20101129083324.6870d7da.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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.