Commit 5823d6eb "add a call to restrict the handle" added a new function
to the foreignmemory API. This API is considered stable and so the new
function should be bound to a new version.
This patch creates version 1.1 of the API, dependent on version 1.0, and
binds the restrict call to version 1.1. Thus version 1.0 is as it was
before the new function was added.
Signed-off-by: Paul Durrant <paul.durr...@citrix.com>
---
Cc: Ian Jackson <ian.jack...@eu.citrix.com>
Cc: Wei Liu <wei.l...@citrix.com>
Cc: Andrew Cooper <andrew.coop...@citrix.com>
---
tools/libs/foreignmemory/libxenforeignmemory.map | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/tools/libs/foreignmemory/libxenforeignmemory.map
b/tools/libs/foreignmemory/libxenforeignmemory.map
index 5c9806c..41a8899 100644
--- a/tools/libs/foreignmemory/libxenforeignmemory.map
+++ b/tools/libs/foreignmemory/libxenforeignmemory.map
@@ -4,6 +4,9 @@ VERS_1.0 {
xenforeignmemory_close;
xenforeignmemory_map;
xenforeignmemory_unmap;
- xenforeignmemory_restrict;
local: *; /* Do not expose anything by default */
};
+VERS_1.1 {
+ global:
+ xenforeignmemory_restrict;
+} VERS_1.0;
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
