public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@ORACLE.COM>
To: Vu Pham <vuhuong@mellanox.com>
Cc: Roland Dreier <rdreier@cisco.com>,
	OpenFabrics EWG <ewg@openfabrics.org>,
	Linux RDMA <linux-rdma@vger.kernel.org>,
	Linux SCSI <linux-scsi@vger.kernel.org>,
	Oren Duer <oren@mellanox.co.il>
Subject: Re: [PATCH v1 10/10] mlx4_fc: Enable FC over Ethernet/Infiniband drivers
Date: Wed, 18 Aug 2010 10:05:34 -0700	[thread overview]
Message-ID: <4C6C12DE.1020209@oracle.com> (raw)
In-Reply-To: <4C6C1096.9090900@mellanox.com>

On 08/18/10 09:55, Vu Pham wrote:
> 
>> 	depends on 
>> +	select LIBFC
>> +	select LIBFCOE
>> +	help
>> +	  Fibre Channel over Ethernet/Infiniband module
>> +
>> +	  This is support for the Mellanox ConnectX/ConnectX-2 HCAs
>> +	  The module will be called mlx4_fc
>>
>> End both lines above with periods (".").
>>
>> +
>> +	  The module FIP-alike to discover BridgeX gateways in the
>> +	  Infiniband fabric
>>
>> end sentence with ".".
>>
>> What does "FIP-alike" mean?  and fix grammar:
>>
>> 	  This module attempts to discover BridgeX gateways in the
>> 	  Infiniband fabric.
>> ?
> 
>>
>> end sentence with ".".
> 
> Thanks for you comments.
> 
> From 54041f56fa1896388a52f503e43e21aa11cc9a2a Mon Sep 17 00:00:00 2001
> From: Vu Pham <vu@vu-lt.mti.mtl.com>
> Date: Tue, 17 Aug 2010 15:40:42 -0700
> Subject: [PATCH 10/10] mlx4_fc: Enable FC over Ethernet/Infiniband drivers
> 
> Add entries in scsi's Kconfig and Makefile to enable mlx4_fc
> (fcoe/fcoib offload driver) and mlx4_fcoib (FIP-alike discovery
> driver)
> 
> Signed-off-by: Vu Pham <vu@mellanox.com>

Looks good.  Thanks for the update.

> ---
>  drivers/scsi/Kconfig  |   23 +++++++++++++++++++++++
>  drivers/scsi/Makefile |    2 ++
>  2 files changed, 25 insertions(+), 0 deletions(-)
> 
> diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig
> index 158284f..e3d2850 100644
> --- a/drivers/scsi/Kconfig
> +++ b/drivers/scsi/Kconfig
> @@ -687,6 +687,29 @@ config FCOE_FNIC
>  	  <file:Documentation/scsi/scsi.txt>.
>  	  The module will be called fnic.
>  
> +config MLX4_FC
> +	tristate "Mellanox FC module"
> +	select MLX4_EN
> +	select LIBFC
> +	select LIBFCOE
> +	help
> +	  Fibre Channel over Ethernet/Infiniband module
> +
> +	  This is support for the Mellanox ConnectX/ConnectX-2 HCAs.
> +	  The module will be called mlx4_fc.
> +
> +config MLX4_FCOIB
> +	tristate "Mellanox FCoIB discovery module"
> +	depends on INFINIBAND
> +	select MLX4_FC
> +	help
> +	  Fibre Channel over Infiniband discovery module
> +
> +	  The module attempts to discover BridgeX gateways in the
> +	  Infiniband fabric by implementing FIP protocol (FCoE
> +	  Initialization protocol) over Infiniband.
> +	  The module will be called mlx4_fcoib.
> +
>  config SCSI_DMX3191D
>  	tristate "DMX3191D SCSI support"
>  	depends on PCI && SCSI
> diff --git a/drivers/scsi/Makefile b/drivers/scsi/Makefile
> index 2a3fca2..0d0dab7 100644
> --- a/drivers/scsi/Makefile
> +++ b/drivers/scsi/Makefile
> @@ -40,6 +40,8 @@ obj-$(CONFIG_LIBFC)		+= libfc/
>  obj-$(CONFIG_LIBFCOE)		+= fcoe/
>  obj-$(CONFIG_FCOE)		+= fcoe/
>  obj-$(CONFIG_FCOE_FNIC)		+= fnic/
> +obj-$(CONFIG_MLX4_FC)		+= mlx4_fc/
> +obj-$(CONFIG_MLX4_FCOIB)	+= mlx4_fc/
>  obj-$(CONFIG_ISCSI_TCP) 	+= libiscsi.o	libiscsi_tcp.o iscsi_tcp.o
>  obj-$(CONFIG_INFINIBAND_ISER) 	+= libiscsi.o
>  obj-$(CONFIG_SCSI_A4000T)	+= 53c700.o	a4000t.o


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

      reply	other threads:[~2010-08-18 17:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-16 22:17 [PATCH v1 10/10] mlx4_fc: Enable FC over Ethernet/Infiniband drivers Vu Pham
2010-08-16 23:51 ` Randy Dunlap
     [not found]   ` <20100816165137.d006efd0.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2010-08-18 16:55     ` Vu Pham
2010-08-18 17:05       ` Randy Dunlap [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C6C12DE.1020209@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=ewg@openfabrics.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=oren@mellanox.co.il \
    --cc=rdreier@cisco.com \
    --cc=vuhuong@mellanox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox