From: Jan Kiszka <jan.kiszka@web.de>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
qemu-devel <qemu-devel@nongnu.org>,
KVM list <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [GIT PULL] kvm upstream updates
Date: Sun, 02 Jan 2011 14:49:03 +0100 [thread overview]
Message-ID: <4D20824F.2080403@web.de> (raw)
In-Reply-To: <4D1DD72C.8000802@web.de>
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
Am 31.12.2010 14:14, Jan Kiszka wrote:
> Am 29.12.2010 16:42, Avi Kivity wrote:
>> On 12/29/2010 05:05 PM, Jan Kiszka wrote:
>>> Am 28.12.2010 11:36, Avi Kivity wrote:
>>>> Marcelo Tosatti (1):
>>>> Expose thread_id in info cpus
>>>
>>> As I'm currently unable to find this particular version of the last
>>> patch in the archive:
>>>
>>> LINK i386-linux-user/qemu-i386
>>> exec.o: In function `cpu_exec_init':
>>> /data/qemu-kvm/exec.c:634: undefined reference to `get_thread_id'
>>>
>>
>> I'll take a look.
>
> OK. And please rebase over current qemu master. I tried to pull in the
> series to prepare qemu-kvm for the back merge, but it generated to much
> conflicts, pointing out that uq/master is outdated.
That was false alarm. Current uq/master actually nicely applies on
qemu/master. My problems turned out to be related to subtle differences
in the qemu-kvm tree.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@web.de>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
KVM list <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: [GIT PULL] kvm upstream updates
Date: Sun, 02 Jan 2011 14:49:03 +0100 [thread overview]
Message-ID: <4D20824F.2080403@web.de> (raw)
In-Reply-To: <4D1DD72C.8000802@web.de>
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
Am 31.12.2010 14:14, Jan Kiszka wrote:
> Am 29.12.2010 16:42, Avi Kivity wrote:
>> On 12/29/2010 05:05 PM, Jan Kiszka wrote:
>>> Am 28.12.2010 11:36, Avi Kivity wrote:
>>>> Marcelo Tosatti (1):
>>>> Expose thread_id in info cpus
>>>
>>> As I'm currently unable to find this particular version of the last
>>> patch in the archive:
>>>
>>> LINK i386-linux-user/qemu-i386
>>> exec.o: In function `cpu_exec_init':
>>> /data/qemu-kvm/exec.c:634: undefined reference to `get_thread_id'
>>>
>>
>> I'll take a look.
>
> OK. And please rebase over current qemu master. I tried to pull in the
> series to prepare qemu-kvm for the back merge, but it generated to much
> conflicts, pointing out that uq/master is outdated.
That was false alarm. Current uq/master actually nicely applies on
qemu/master. My problems turned out to be related to subtle differences
in the qemu-kvm tree.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2011-01-02 13:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 10:36 [GIT PULL] kvm upstream updates Avi Kivity
2010-12-28 10:36 ` [Qemu-devel] " Avi Kivity
2010-12-29 15:05 ` Jan Kiszka
2010-12-29 15:05 ` [Qemu-devel] " Jan Kiszka
2010-12-29 15:42 ` Avi Kivity
2010-12-29 15:42 ` [Qemu-devel] " Avi Kivity
2010-12-31 13:14 ` Jan Kiszka
2010-12-31 13:14 ` [Qemu-devel] " Jan Kiszka
2011-01-02 13:49 ` Jan Kiszka [this message]
2011-01-02 13:49 ` Jan Kiszka
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=4D20824F.2080403@web.de \
--to=jan.kiszka@web.de \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.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.