xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: "Keir (Xen.org)" <keir@xen.org>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Konrad Wilk <konrad.wilk@oracle.com>,
	"Tim (Xen.org)" <tim@xen.org>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Jan Beulich <JBeulich@suse.com>,
	Zhigang Wang <zhigang.x.wang@oracle.com>
Subject: Re: Please ack XENMEM_claim_pages hypercall?
Date: Tue, 27 Nov 2012 14:46:05 +0000	[thread overview]
Message-ID: <50B4D22D.20809@eu.citrix.com> (raw)
In-Reply-To: <4e524dad-b67a-4115-b0fd-72f9b372abf1@default>

On 27/11/12 14:38, Dan Magenheimer wrote:
> Now, with that in mind, I still haven't heard any objections
> other than insufficient testing (fair, but also very true of
> most patches accepted into xen-unstable months before a release);
> and "your toolstack should use the 'Citrix paradigm'" (and
> I believe I have adequately explained why we cannot).  Are
> there other valid objections?

Yes -- the main one being, you have not convinced anyone it's necessary 
yet.  Maybe you should ask someone else to take up this cause -- we seem 
to have major problems communicating with you.

  -George

  reply	other threads:[~2012-11-27 14:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26 19:07 Please ack XENMEM_claim_pages hypercall? Dan Magenheimer
2012-11-27  8:48 ` Jan Beulich
2012-11-27 10:22   ` Keir Fraser
2012-11-27 14:08     ` Dan Magenheimer
2012-11-27 14:47       ` Keir Fraser
2012-11-27 10:31   ` Ian Campbell
2012-11-27 14:15     ` Tim Deegan
2012-11-27 14:38     ` Dan Magenheimer
2012-11-27 14:46       ` George Dunlap [this message]
2012-11-29 16:00       ` Ian Jackson
2012-12-03 15:45         ` Dan Magenheimer
2012-11-27 14:06   ` Dan Magenheimer

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=50B4D22D.20809@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=keir@xen.org \
    --cc=konrad.wilk@oracle.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.org \
    --cc=zhigang.x.wang@oracle.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 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).