All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 2/4] docs/html/hcall: Annotations for two hypercalls
Date: Mon, 14 Nov 2011 13:40:57 -0500	[thread overview]
Message-ID: <20111114184057.GB15284@phenom.dumpdata.com> (raw)
In-Reply-To: <1321212066-10648-3-git-send-email-ian.jackson@eu.citrix.com>

On Sun, Nov 13, 2011 at 07:21:04PM +0000, Ian Jackson wrote:
> Add annotations for a couple of the hypercalls:
>  HYPERVISOR_set_trap_table
>  HYPERVISOR_mmu_update

So I've some comments on the affects of what this hypercall expects
in some details. Where would I put those? In the header file or should
I do it somewhere else?

  parent reply	other threads:[~2011-11-14 18:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-13 19:21 [PATCH 0/4] docs/html/hcall: Hypercall docs headers Ian Jackson
2011-11-13 19:21 ` [PATCH 1/4] docs/html/hcall: Initial cut of header documentation massager Ian Jackson
2011-11-14  9:59   ` Ian Campbell
2011-11-14 17:20     ` Ian Jackson
2011-11-13 19:21 ` [PATCH 2/4] docs/html/hcall: Annotations for two hypercalls Ian Jackson
2011-11-14 10:12   ` Ian Campbell
2011-11-14 17:22     ` Ian Jackson
2011-11-14 18:40   ` Konrad Rzeszutek Wilk [this message]
2011-11-15 14:47     ` Ian Jackson
2011-11-15 15:00       ` Konrad Rzeszutek Wilk
2011-11-29 14:21         ` Ian Jackson
2011-11-13 19:21 ` [PATCH 3/4] docs/html/hcall: Generate an "index.html" Ian Jackson
2011-11-14 10:13   ` Ian Campbell
2011-11-14 17:23     ` Ian Jackson
2011-11-13 19:21 ` [PATCH 4/4] docs/html/hcall: Arrange for automatic build Ian Jackson
2011-11-14 10:13 ` [PATCH 0/4] docs/html/hcall: Hypercall docs headers Ian Campbell
2011-11-14 17:24   ` Ian Jackson

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=20111114184057.GB15284@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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.