xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Andres Lagar-Cavilla <andres@lagarcavilla.org>
Cc: xen-devel@lists.xensource.com, ian.campbell@citrix.com,
	andres@gridcentric.ca, tim@xen.org, keir.xen@gmail.com,
	ian.jackson@citrix.com, adin@gridcentric.ca
Subject: Re: [PATCH 1 of 7] Tools: Sanitize mem_event/access/paging interfaces
Date: Thu, 23 Feb 2012 15:29:18 +0100	[thread overview]
Message-ID: <20120223142918.GA25289@aepfle.de> (raw)
In-Reply-To: <3b24188d8815aa5a5abb.1329977106@xdev.gridcentric.ca>

On Thu, Feb 23, Andres Lagar-Cavilla wrote:

> In-tree consumers (xenpaging, xen-access) updated. This is an ABI/API change,
> so please voice any concerns.

Too many changes already since 4.1, out of tree binaries are already
covered by bumped SONAME and bumped domctl version.

Acked-by: Olaf Hering <olaf@aepfle.de>

  reply	other threads:[~2012-02-23 14:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23  6:05 [PATCH 0 of 7] Mem event ring setup interface update Andres Lagar-Cavilla
2012-02-23  6:05 ` [PATCH 1 of 7] Tools: Sanitize mem_event/access/paging interfaces Andres Lagar-Cavilla
2012-02-23 14:29   ` Olaf Hering [this message]
2012-02-28 12:56   ` Ian Campbell
2012-02-28 15:14     ` Andres Lagar-Cavilla
2012-02-23  6:05 ` [PATCH 2 of 7] x86/hvm: refactor calls to prepare and tear down a helper ring Andres Lagar-Cavilla
2012-02-23  6:05 ` [PATCH 3 of 7] Use a reserved pfn in the guest address space to store mem event rings Andres Lagar-Cavilla
2012-02-28 13:01   ` Ian Campbell
2012-02-28 15:19     ` Andres Lagar-Cavilla
2012-03-01  7:47       ` Ian Campbell
2012-03-01 15:17         ` Tim Deegan
2012-03-01 16:26           ` Andres Lagar-Cavilla
2012-03-01 16:30           ` Andres Lagar-Cavilla
2012-03-01 17:32             ` Tim Deegan
2012-03-01 17:44               ` Andres Lagar-Cavilla
2012-03-01 17:52                 ` [PATCH 3 of 7] Use a reserved pfn in the guest address space to store mem event ringsg Tim Deegan
2012-03-06 19:27                   ` Andres Lagar-Cavilla
2012-03-01  2:29     ` [PATCH 3 of 7] Use a reserved pfn in the guest address space to store mem event rings Andres Lagar-Cavilla
2012-02-23  6:05 ` [PATCH 4 of 7] x86/mm: wire up sharing ring Andres Lagar-Cavilla
2012-02-23  6:05 ` [PATCH 5 of 7] Tools: libxc side for setting up the mem " Andres Lagar-Cavilla
2012-02-28 13:02   ` Ian Campbell
2012-02-23  6:05 ` [PATCH 6 of 7] x86/mm: Clean up mem event structures on domain destruction Andres Lagar-Cavilla
2012-02-23 14:32   ` Olaf Hering
2012-02-23  6:05 ` [PATCH 7 of 7] x86/mm: Fix mem event error message typos Andres Lagar-Cavilla
2012-02-23 16:07 ` [PATCH 0 of 7] Mem event ring setup interface update Tim Deegan
2012-02-27 22:43   ` Andres Lagar-Cavilla
  -- strict thread matches above, loose matches on Subject: below --
2012-03-01  2:43 [PATCH 0 of 7] Mem event ring interface setup update, V2 Andres Lagar-Cavilla
2012-03-01  2:43 ` [PATCH 1 of 7] Tools: Sanitize mem_event/access/paging interfaces 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=20120223142918.GA25289@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=adin@gridcentric.ca \
    --cc=andres@gridcentric.ca \
    --cc=andres@lagarcavilla.org \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=keir.xen@gmail.com \
    --cc=tim@xen.org \
    --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 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).