Version: 1
-Previous: 0ab055876e097424bd5ba9bc16455ac307d871bb
-Head: 36d9228ec7d95954d1c52ef9fce6f32d56a0412b
+Previous: edc4db9d68585e0cb4dc66aff4ef5a06e004e7cb
+Head: 4267e3692ddda2b22cfd7713c01d4759818dc783
Applied:
af_ib: fb683ba55480ada43c09aa48b3cb18bde139f72c
rename-ibacm: 045b8745bb159da2fdeee216007c10f1a058d547
fixup-man: 36d9228ec7d95954d1c52ef9fce6f32d56a0412b
+ refresh-temp: 4267e3692ddda2b22cfd7713c01d4759818dc783
Unapplied:
dev-name2ip: 8e00708e882239292492e13aa51c82042255933c
dev-addrsize: 8de02c47fbf595132105a7050ad6f755f49f9a7a
--- /dev/null
+Bottom: 2724258e9ed52f80159968b8b63216a7ba8595a6
+Top: dbd12c9e450afa12621e35dbb8cd04c4f28365ad
+Author: Sean Hefty <sean.hefty@intel.com>
+Date: 2012-03-01 16:57:08 -0800
+
+Refresh of fixup-man
+
+---
+
+diff --git a/man/ibacm.7 b/man/ibacm.7
+index 22c28a3..c0c63fc 100644
+--- a/man/ibacm.7
++++ b/man/ibacm.7
+@@ -17,9 +17,8 @@ similar to rdma_getaddrinfo, rdma_resolve_addr, and rdma_resolve_route using
+ IB multicast.\r
+ The IB ACM does not require IPoIB or use standard naming services, such as\r
+ DNS, and limits network communication, especially with the IB SA.\r
+-Because it uses multicast traffic and limits SA interaction, it may\r
+-not support all cluster configurations. The ib_acme utility assists in\r
+-verifying what options of the ibacm service may be usable.\r
++The ib_acme utility assists in verifying what options of the ibacm service\r
++may be usable for the current fabric topology.\r
+ .P\r
+ Client interactions with the ibacm service are done over sockets through\r
+ a standard TCP connection. The librdmacm abstracts this interaction.\r
+@@ -29,5 +28,4 @@ success
+ .IP "!= 0"\r
+ error\r
+ .SH "SEE ALSO"\r
+-ib_acm_resolve_name(3), ib_acm_resolve_ip(3), ib_acm_resolve_path(3)\r
+ ib_acme(1), ibacm(1)