[openib-general] [PATCH] iwarp branch - Kconfig + README fixes

Steve Wise swise at ammasso.com
Mon Aug 8 10:31:43 PDT 2005


Tom,

Here is a patch that fixes Kconfig and the README typos.  I didn't test it.

Signed-off-by: Steve Wise <swise at ammasso.com>

Index: Kconfig
===================================================================
--- Kconfig     (revision 3015)
+++ Kconfig     (working copy)
@@ -3,13 +3,13 @@
        depends on PCI && INFINIBAND
        ---help---
          This is a low-level driver for the Ammasso 1100 host
-         channel adapters (HCAs).
+         channel adapter (HCA).
 
 config INFINIBAND_AMSO1100_DEBUG
        bool "Verbose debugging output"
        depends on INFINIBAND_AMSO1100
        default n
        ---help---
-         This option causes the mthca driver produce a bunch of debug
-         messages.  Select this is you are developing the driver or
-         trying to diagnose a problem.
+         This option causes the amso1100 driver to produce a bunch of
+         debug messages.  Select this if you are developing the driver
+         or trying to diagnose a problem.
Index: README
===================================================================
--- README      (revision 3015)
+++ README      (working copy)
@@ -1,13 +1,13 @@
 
-This is starting point for the OpenIB iWARP driver for the AMSO1100 HCA
-from Ammasso. The adapter is a 1Gb RDMA capable PCI-X NIC.
+This is a starting point for the OpenIB iWARP driver for the AMSO1100
+HCA from Ammasso. The adapter is a 1Gb RDMA capable PCI-X NIC.
 
 The driver in its original form contains a netdev driver for native
 stack support, a set of kDAT services, and a set of Ammasso verbs that
 are based on the RDMAC verbs.  That said, it should be clear that this
 driver was originally developed for a different environment (standalone)
 with a different set of goals and objectives than those for which it is
-not being tasked. It was also developed to reuse as much code as possible
+now being tasked. It was also developed to reuse as much code as possible
 between the user mode and kernel mode pieces of the product. This is
 why the naming conventions for the files (and some of the functions)
 is so whacky. xyz_common.c for example, and fname_kern() instead of




More information about the general mailing list