Version: 1
-Previous: 16364c491816eab272b0d6ec7ae16c99f0fa5c21
-Head: a7e0185569691d8ceaefd9e10d9a939efb4054db
+Previous: bbb4fd31e33d1f1b4daf9050f73a3b7b348932c1
+Head: 802bdd740a7cf76e8ef381a4dd1b677074878df8
Applied:
notes: a7e0185569691d8ceaefd9e10d9a939efb4054db
+ refresh-temp: 802bdd740a7cf76e8ef381a4dd1b677074878df8
Unapplied:
Hidden:
--- /dev/null
+Bottom: 40ad6411b2dade22b07ae91785cc9c8f11f32df8
+Top: 087d6d362bd4701b1c1d2e3b02fbb873888cbf80
+Author: Sean Hefty <sean.hefty@intel.com>
+Date: 2010-06-08 11:59:32 -0700
+
+Refresh of notes
+
+---
+
+diff --git a/acm_notes.txt b/acm_notes.txt
+index c7dc56a..bf38961 100644
+--- a/acm_notes.txt
++++ b/acm_notes.txt
+@@ -89,7 +89,7 @@ ib_acm supports standard SA path record queries on the back-end, it
+ provides an experimental multicast resolution protocol in hope of\r
+ achieving greater scalability. The latter is not usable on all fabric\r
+ topologies, specifically ones that may not have reversible paths.\r
+-Users should use the ib_acme utilty to verify that multicast protocol\r
++Users should use the ib_acme utility to verify that multicast protocol\r
+ is usable before running other applications.\r
+ \r
+ Conceptually, the ib_acm service implements an ARP like protocol and either