From: Ian Campbell <Ian.Campbell@citrix.com>
To: Andres Lagar-Cavilla <andres@lagarcavilla.org>
Cc: "xen-devel@xen.lists.org" <xen-devel@xen.lists.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
David Vrabel <david.vrabel@citrix.com>,
David Miller <davem@davemloft.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] Xen backend support for paged out grant targets.
Date: Thu, 13 Sep 2012 19:11:39 +0100 [thread overview]
Message-ID: <1347559899.25803.64.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <1347557306-25453-1-git-send-email-andres@lagarcavilla.org>
On Thu, 2012-09-13 at 18:28 +0100, Andres Lagar-Cavilla wrote:
>
> * Add placeholder in array of grant table error descriptions for
> unrelated error code we jump over.
Why not just define it, it's listed here:
http://xenbits.xen.org/docs/unstable/hypercall/include,public,grant_table.h.html#Enum_grant_status
I notice the specific wording of the error msg is different here too.
It'd probably be best to use the same wording as the Xen definition, so
all OSes end up with the same name for the same condition (else bug
reports will be confusing).
Ian.
next prev parent reply other threads:[~2012-09-13 18:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 17:28 [PATCH] Xen backend support for paged out grant targets Andres Lagar-Cavilla
2012-09-13 18:11 ` Ian Campbell [this message]
2012-09-13 19:45 ` Andres Lagar-Cavilla
2012-09-14 7:19 ` Ian Campbell
2012-09-14 12:44 ` Konrad Rzeszutek Wilk
2012-09-14 14:27 ` Andres Lagar-Cavilla
[not found] <1347479153-441-1-git-send-email-andres@lagarcavilla.org>
2012-09-12 20:06 ` Konrad Rzeszutek Wilk
2012-09-12 20:21 ` Andres Lagar-Cavilla
2012-09-13 0:04 ` Andres Lagar-Cavilla
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=1347559899.25803.64.camel@dagon.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=andres@lagarcavilla.org \
--cc=davem@davemloft.net \
--cc=david.vrabel@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xen-devel@xen.lists.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).