From: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
To: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
Cc: Rob Landley <rob@landley.net>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Alexander Graf <agraf@suse.de>,
Randy Dunlap <rdunlap@xenotime.net>, KVM <kvm@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Gleb Natapov <gleb@redhat.com>, Ingo Molnar <mingo@redhat.com>,
Avi Kivity <avi@redhat.com>, Jan Kiszka <jan.kiszka@siemens.com>,
X86 <x86@kernel.org>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 0/3] Documentation : hypercalls
Date: Tue, 07 Aug 2012 13:22:17 +0530 [thread overview]
Message-ID: <5020C931.6030503@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120807073946.20169.72958.sendpatchset@codeblue.in.ibm.com>
On 08/07/2012 01:09 PM, Raghavendra K T wrote:
> This is the hypercall documentation patch series
> First patch covers KVM specific hypercall information.
>
> second patch has typo fix for vmcall instruction
> comment in kvm_para.h
>
> Third patch includes a very useful documentation on PowerPC
> hypercalls originally written by Alex
next prev parent reply other threads:[~2012-08-07 7:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 7:39 [PATCH 0/3] Documentation : hypercalls Raghavendra K T
2012-08-07 7:39 ` [PATCH 1/3] Documentation/kvm : Add documentation on hypercalls Raghavendra K T
2012-08-07 7:40 ` [PATCH 2/3] Documentation/header : Correct vmrun to vmcall typo Raghavendra K T
2012-08-07 7:40 ` [PATCH 2/3] Documentation/ppc: Add ppc hypercall documentation Raghavendra K T
2012-08-07 7:43 ` [PATCH 3/3] " Raghavendra K T
2012-08-07 7:52 ` Raghavendra K T [this message]
2012-08-09 18:31 ` [PATCH 0/3] Documentation : hypercalls Marcelo Tosatti
2012-08-11 9:59 ` Raghavendra K T
2012-08-13 20:40 ` Marcelo Tosatti
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=5020C931.6030503@linux.vnet.ibm.com \
--to=raghavendra.kt@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=hpa@zytor.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=rdunlap@xenotime.net \
--cc=rob@landley.net \
--cc=tglx@linutronix.de \
--cc=x86@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.