All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Philipson <Ross.Philipson@citrix.com>
To: Tim Deegan <Tim.Deegan@eu.citrix.com>
Cc: James,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	McKenzie <James.McKenzie@citrix.com>
Subject: RE: [PATCH 1/1] Reserve V4V hypercall number
Date: Wed, 13 Jul 2011 11:27:31 -0400	[thread overview]
Message-ID: <831D55AF5A11D64C9B4B43F59EEBF720724926C146@FTLPMAILBOX02.citrite.net> (raw)
In-Reply-To: <20110713152454.GA10754@whitby.uk.xensource.com>

OK, I will resubmit with language like that. I also forgot the VIRQ we use...

Thanks
Ross

-----Original Message-----
From: Tim Deegan 
Sent: Wednesday, July 13, 2011 11:25 AM
To: Ross Philipson
Cc: xen-devel@lists.xensource.com; James McKenzie
Subject: Re: [Xen-devel] [PATCH 1/1] Reserve V4V hypercall number

At 11:03 -0400 on 13 Jul (1310554989), Ross Philipson wrote:
> Reserve the V4V hypercall number to prevent its use prior to the 
> up-streaming of the rest of the V4V functionality.

When can we expect patches for the actual hypercall?  If it's not imminent, if would be better to use language like 22626:ceb508436e6e so as not to confuse readers of the code.  

Cheers,

Tim.

--
Tim Deegan <Tim.Deegan@citrix.com>
Principal Software Engineer, Xen Platform Team Citrix Systems UK Ltd.  (Company #02937203, SL9 0BG)

      reply	other threads:[~2011-07-13 15:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13 15:03 [PATCH 1/1] Reserve V4V hypercall number Ross Philipson
2011-07-13 15:24 ` Tim Deegan
2011-07-13 15:27   ` Ross Philipson [this message]

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=831D55AF5A11D64C9B4B43F59EEBF720724926C146@FTLPMAILBOX02.citrite.net \
    --to=ross.philipson@citrix.com \
    --cc=James.McKenzie@citrix.com \
    --cc=Tim.Deegan@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.