[Pkg-ofed-commits] [libfabric] 100/123: fi_usnic(7): fix bullet indenting

[Ana Beatriz Guerrero López]

This is an automated email from the git hooks/post-receive script.

ana pushed a commit to annotated tag v1.1.1
in repository libfabric.

commit 3d39df456ce16621933fe0db30837d9b20c430b0
Author: Dave Goodell <dgoodell at cisco.com>
Date:   Mon Sep 28 15:20:01 2015 -0700

    fi_usnic(7): fix bullet indenting
    
    This patch is best viewed with the `-w` or `-b` options to `git diff`,
    `git show`, etc.
    
    Signed-off-by: Dave Goodell <dgoodell at cisco.com>
---
 man/fi_usnic.7.md | 78 +++++++++++++++++++++++++++----------------------------
 1 file changed, 39 insertions(+), 39 deletions(-)

diff --git a/man/fi_usnic.7.md b/man/fi_usnic.7.md
index ce9ead3..c408cac 100644
--- a/man/fi_usnic.7.md
+++ b/man/fi_usnic.7.md
@@ -20,51 +20,51 @@ low latency and other offload capabilities on Ethernet networks.
 
 * The *usnic* libfabric provider requires the use of the "libnl"
   library.
-  * There are two versions of libnl generally available: v1 and v3;
-    the usnic provider can use either version.
-  * If you are building libfabric/the usnic provider from source, you
-    will need to have the libnl header files available (e.g., if you
-    are installing libnl from RPM or other packaging system, install
-    the "-devel" versions of the package).
-  * If you have libnl (either v1 or v3) installed in a non-standard
-    location (e.g., not in /usr/lib or /usr/lib64), you may need to
-    tell libfabric's configure where to find libnl via the
-    `--with-libnl=DIR` command line option (where DIR is the
-    installation prefix of the libnl package).
+    * There are two versions of libnl generally available: v1 and v3;
+      the usnic provider can use either version.
+    * If you are building libfabric/the usnic provider from source, you
+      will need to have the libnl header files available (e.g., if you
+      are installing libnl from RPM or other packaging system, install
+      the "-devel" versions of the package).
+    * If you have libnl (either v1 or v3) installed in a non-standard
+      location (e.g., not in /usr/lib or /usr/lib64), you may need to
+      tell libfabric's configure where to find libnl via the
+      `--with-libnl=DIR` command line option (where DIR is the
+      installation prefix of the libnl package).
 * The most common way to use the libfabric usnic provider is via an
   MPI implementation that uses libfabric (and the usnic provider) as a
   lower layer transport.  MPI applications do not need to know
   anything about libfabric or usnic in this use case -- the MPI
   implementation hides all these details from the application.
 * If you are writing applications directly to the libfabric API:
-  * *FI_EP_DGRAM* endpoints are the best supported method of utilizing
-    the usNIC interface.  Specifically, the *FI_EP_DGRAM* endpoint
-    type has been extensively tested as the underlying layer for Open
-    MPI's *usnic* BTL.
-  * *FI_EP_MSG* and *FI_EP_RDM* endpoints are implemented, but are
-    only lightly tested.  It is likely that there are still some bugs
-    in these endpoint types.  RMA is not yet supported.
-  * *FI_EP_RDM* support is not 100% robust and occasionally leads to hangs in
-    the `fi_rdm_pingpong` test from fabtests.
-  * [`fi_provider`(7)](fi_provider.7.html) lists requirements for all
-    providers.  The following limitations exist in the *usnic*
-    provider:
-    * multicast operations are not supported on *FI_EP_DGRAM* and
-      *FI_EP_RDM* endpoints.
-    * *FI_EP_MSG* endpoints only support connect, accept, getname, and
-      shutdown CM operations.
-    * Passive endpoints only support listen, setname, and getname CM
-      operations.
-    * *FI_EP_DGRAM* endpoints support `fi_sendmsg()` and
-      `fi_recvmsg()`, but all flags are ignored.
-    * Address vectors only support `FI_AV_MAP`.
-    * No counters are supported.
-    * The tag matching interface is not supported.
-    * *FI_MSG_PREFIX* is only supported on *FI_EP_DGRAM* and usage
-      is limited to the 1.1 release.
-  * The usnic libfabric provider supports extensions that provide
-    information and functionality beyond the standard libfabric
-    interface.  See the "USNIC EXTENSIONS" section, below.
+    * *FI_EP_DGRAM* endpoints are the best supported method of utilizing
+      the usNIC interface.  Specifically, the *FI_EP_DGRAM* endpoint
+      type has been extensively tested as the underlying layer for Open
+      MPI's *usnic* BTL.
+    * *FI_EP_MSG* and *FI_EP_RDM* endpoints are implemented, but are
+      only lightly tested.  It is likely that there are still some bugs
+      in these endpoint types.  RMA is not yet supported.
+    * *FI_EP_RDM* support is not 100% robust and occasionally leads to hangs in
+      the `fi_rdm_pingpong` test from fabtests.
+    * [`fi_provider`(7)](fi_provider.7.html) lists requirements for all
+      providers.  The following limitations exist in the *usnic*
+      provider:
+        * multicast operations are not supported on *FI_EP_DGRAM* and
+          *FI_EP_RDM* endpoints.
+        * *FI_EP_MSG* endpoints only support connect, accept, getname, and
+          shutdown CM operations.
+        * Passive endpoints only support listen, setname, and getname CM
+          operations.
+        * *FI_EP_DGRAM* endpoints support `fi_sendmsg()` and
+          `fi_recvmsg()`, but all flags are ignored.
+        * Address vectors only support `FI_AV_MAP`.
+        * No counters are supported.
+        * The tag matching interface is not supported.
+        * *FI_MSG_PREFIX* is only supported on *FI_EP_DGRAM* and usage
+          is limited to the 1.1 release.
+    * The usnic libfabric provider supports extensions that provide
+      information and functionality beyond the standard libfabric
+      interface.  See the "USNIC EXTENSIONS" section, below.
 
 # USNIC EXTENSIONS
 

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-ofed/libfabric.git