From: Avi Kivity <avi@qumranet.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org,
Jerone Young <jyoung5@us.ibm.com>
Subject: Re: [PATCH] [v2] Remove use of bit fields in kvm trace structure
Date: Sat, 05 Jul 2008 09:37:55 +0000 [thread overview]
Message-ID: <486F40F3.2040407@qumranet.com> (raw)
In-Reply-To: <1214409353.1746.5.camel@localhost.localdomain>
Hollis Blanchard wrote:
> Avi, if this is OK now, please also apply Jerone's earlier patches:
> [PATCH 2 of 3] Move KVM TRACE DEFINITIONS to common header
> [PATCH 3 of 3] Add new KVM TRACE events
> (and add my Acked-by to those as well).
>
>
I've lost the thread, so please repost any missing patches.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@qumranet.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org,
Jerone Young <jyoung5@us.ibm.com>
Subject: Re: [PATCH] [v2] Remove use of bit fields in kvm trace structure
Date: Sat, 05 Jul 2008 12:37:55 +0300 [thread overview]
Message-ID: <486F40F3.2040407@qumranet.com> (raw)
In-Reply-To: <1214409353.1746.5.camel@localhost.localdomain>
Hollis Blanchard wrote:
> Avi, if this is OK now, please also apply Jerone's earlier patches:
> [PATCH 2 of 3] Move KVM TRACE DEFINITIONS to common header
> [PATCH 3 of 3] Add new KVM TRACE events
> (and add my Acked-by to those as well).
>
>
I've lost the thread, so please repost any missing patches.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-07-05 9:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 18:54 [PATCH] [v2] Remove use of bit fields in kvm trace structure Jerone Young
2008-06-24 18:54 ` Jerone Young
2008-06-25 15:55 ` Hollis Blanchard
2008-06-25 15:55 ` Hollis Blanchard
2008-07-05 9:37 ` Avi Kivity [this message]
2008-07-05 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=486F40F3.2040407@qumranet.com \
--to=avi@qumranet.com \
--cc=hollisb@us.ibm.com \
--cc=jyoung5@us.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.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.