From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] KVM API documentation patches
Date: Thu, 11 Sep 2014 15:58:02 -0700 [thread overview]
Message-ID: <20140911225802.GU5535@lvm> (raw)
In-Reply-To: <54101B3D.20000@redhat.com>
On Wed, Sep 10, 2014 at 11:34:53AM +0200, Paolo Bonzini wrote:
> Il 09/09/2014 18:27, Alex Benn?e ha scritto:
> > Hi,
> >
> > I'm preparing to add ARM KVM GDB support and I went to read the API
> > documentation and found it surprisingly mute on the subject ;-)
> >
> > The first patch documents the "new" KVM_SET_GUEST_DEBUG ioctl based on
> > reviewing the code. I've included a long CC list of people who've
> > actually done the various implementations who I hope can sanity check
> > the write-up. The second is a trivial formatting fix for what looks
> > like a minor merge trip-up.
> >
> > Alex Benn?e (2):
> > KVM: document KVM_SET_GUEST_DEBUG api
> > KVM: fix api documentation of KVM_GET_EMULATED_CPUID
> >
> > Documentation/virtual/kvm/api.txt | 184 +++++++++++++++++++++++---------------
> > 1 file changed, 114 insertions(+), 70 deletions(-)
> >
>
> Thanks, applying both!
>
ha, read this after reviewing his text. Was I too nit-picky? ;)
-Christoffer
next prev parent reply other threads:[~2014-09-11 22:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 16:27 [PATCH 0/2] KVM API documentation patches Alex Bennée
2014-09-09 16:27 ` [PATCH 1/2] KVM: document KVM_SET_GUEST_DEBUG api Alex Bennée
2014-09-11 22:56 ` Christoffer Dall
2014-09-09 16:27 ` [PATCH 2/2] KVM: fix api documentation of KVM_GET_EMULATED_CPUID Alex Bennée
2014-09-09 19:11 ` Borislav Petkov
2014-09-10 9:34 ` [PATCH 0/2] KVM API documentation patches Paolo Bonzini
2014-09-11 22:58 ` Christoffer Dall [this message]
2014-09-15 15:56 ` Alex Bennée
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=20140911225802.GU5535@lvm \
--to=christoffer.dall@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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 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).