From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Sasha Levin <levinsasha928@gmail.com>,
"kvm@vger.kernel.org list" <kvm@vger.kernel.org>,
kvm-ppc@vger.kernel.org
Subject: Re: [PATCH] KVM: Update documentation to include detailed ENABLE_CAP
Date: Wed, 31 Aug 2011 13:07:55 +0000 [thread overview]
Message-ID: <4E5E322B.1020706@redhat.com> (raw)
In-Reply-To: <8C6F81F0-4FA0-4E2A-A1DB-4A525AE0152E@suse.de>
On 08/31/2011 04:02 PM, Alexander Graf wrote:
> On 31.08.2011, at 14:52, Sasha Levin wrote:
>
> > On Wed, 2011-08-31 at 10:58 +0200, Alexander Graf wrote:
> >> +This capaobility enables interception of OSI hypercalls that otherwise would
> > capability
>
> Oops :). Avi, you pulled that one in already. Can you still change it in-tree (it's not gone to master yet, right?) or do you want me to send a typo fix patch on top?
>
I fixed it locally here, and no it wasn't pushed yet.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Sasha Levin <levinsasha928@gmail.com>,
"kvm@vger.kernel.org list" <kvm@vger.kernel.org>,
kvm-ppc@vger.kernel.org
Subject: Re: [PATCH] KVM: Update documentation to include detailed ENABLE_CAP description
Date: Wed, 31 Aug 2011 16:07:55 +0300 [thread overview]
Message-ID: <4E5E322B.1020706@redhat.com> (raw)
In-Reply-To: <8C6F81F0-4FA0-4E2A-A1DB-4A525AE0152E@suse.de>
On 08/31/2011 04:02 PM, Alexander Graf wrote:
> On 31.08.2011, at 14:52, Sasha Levin wrote:
>
> > On Wed, 2011-08-31 at 10:58 +0200, Alexander Graf wrote:
> >> +This capaobility enables interception of OSI hypercalls that otherwise would
> > capability
>
> Oops :). Avi, you pulled that one in already. Can you still change it in-tree (it's not gone to master yet, right?) or do you want me to send a typo fix patch on top?
>
I fixed it locally here, and no it wasn't pushed yet.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-08-31 13:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 8:58 [PATCH] KVM: Update documentation to include detailed ENABLE_CAP description Alexander Graf
2011-08-31 8:58 ` Alexander Graf
2011-08-31 12:52 ` [PATCH] KVM: Update documentation to include detailed Sasha Levin
2011-08-31 12:52 ` [PATCH] KVM: Update documentation to include detailed ENABLE_CAP description Sasha Levin
2011-08-31 13:02 ` Alexander Graf
2011-08-31 13:02 ` Alexander Graf
2011-08-31 13:07 ` Avi Kivity [this message]
2011-08-31 13:07 ` Avi Kivity
2011-08-31 13:11 ` Alexander Graf
2011-08-31 13:11 ` Alexander Graf
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=4E5E322B.1020706@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
/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.