public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Moger, Babu" <Babu.Moger@lsi.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"sekharan@us.ibm.com" <sekharan@us.ibm.com>,
	"andmike@linux.vnet.ibm.com" <andmike@linux.vnet.ibm.com>,
	device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH] scsi_dh: Adding LSI vendor and product ids in  rdac device list
Date: Mon, 24 Nov 2008 09:04:45 +0900	[thread overview]
Message-ID: <1227485085.25499.5.camel@localhost.localdomain> (raw)
In-Reply-To: <E463DF2B2E584B4A82673F53D62C2EF45BE75982@cosmail01.lsi.com>

On Mon, 2008-11-10 at 16:17 -0700, Moger, Babu wrote:
> From: Babu Moger <babu.moger@lsi.com>
> 
> This patch adds LSI vendor and product ids in rdac device handler.
> 
> Signed-off-by: Babu Moger <Babu.Moger@lsi.com>
> 
> ---
> 
> --- linux-2.6.28-rc4/drivers/scsi/device_handler/scsi_dh_rdac.c.orig    2008-11-10 16:56:01.000000000 -0600
> +++ linux-2.6.28-rc4/drivers/scsi/device_handler/scsi_dh_rdac.c 2008-11-10 16:56:20.000000000 -0600
> @@ -594,6 +594,8 @@ static const struct scsi_dh_devlist rdac
>         {"SUN", "LCSM100_F"},
>         {"DELL", "MD3000"},
>         {"DELL", "MD3000i"},
> +       {"LSI", "INF-01-00"},
> +       {"ENGENIO", "INF-01-00"},
>         {NULL, NULL},
>  };

This patch is whitespace damaged.  Your tabs have been converted to
spaces by your email tool.  I've fixed it up this time, since it was
only two lines, but please see

Documentation/email-clients.txt

For hints on how to get your MUA to work with patches.

James



  reply	other threads:[~2008-11-24  0:04 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06  4:05 [PATCH] Make sure the state of a path is set properly when controller is swapped from passive to active Chandra Seetharaman
2008-11-10 23:17 ` [PATCH] scsi_dh: Adding LSI vendor and product ids in rdac device list Moger, Babu
2008-11-24  0:04   ` James Bottomley [this message]
2008-11-24 15:06     ` Moger, Babu
2008-11-11  0:45 ` DM does not activate the paths if there are more than one path in path group during failover Moger, Babu
2008-11-11  0:59   ` Alasdair G Kergon
2008-11-11 17:13     ` Moger, Babu
2008-11-11 21:00       ` Chandra Seetharaman
2008-11-13 23:48       ` [RFC][PATCH] Handle multipath paths in a path group properly during pg_init (was "RE: [dm-devel] DM does not activate the paths if there are more than one path in path group during failover") Chandra Seetharaman
2008-11-14  0:12         ` [RFC][PATCH] Handle multipath paths in a path group properly during pg_init (was "RE: " Alasdair G Kergon
2008-11-14 19:08           ` [RFC][PATCH] Handle multipath paths in a path group properly during pg_init (was "RE: [dm-devel] " Chandra Seetharaman
2008-11-14 19:34             ` [RFC][PATCH] Handle multipath paths in a path group properly during pg_init (was "RE: " Alasdair G Kergon
2008-11-14 20:24               ` [RFC][PATCH] Handle multipath paths in a path group properly during pg_init (was "RE: [dm-devel] " Chandra Seetharaman
2008-11-11  2:06   ` DM does not activate the paths if there are more than one path in path group during failover Chandra Seetharaman
2008-11-11 17:07     ` Moger, Babu
2008-11-11 17:10       ` Chandra Seetharaman
2008-11-11 17:28         ` Moger, Babu
2009-01-22  0:00 ` qla2xxx 0000:03:0c.0: Firmware image unavailable Moger, Babu
2009-01-22  0:26   ` Seokmann Ju
2009-01-22 14:14     ` Moger, Babu
2009-01-22 14:39       ` Sudhakar Pannerselvam
2009-01-22 15:20         ` Moger, Babu
2009-01-22 16:46           ` Dave Holland
2009-01-23  0:15             ` [dm-devel] " Moger, Babu
2009-01-23  6:22               ` Sudhakar Pannerselvam
2009-01-23 15:04                 ` James Bottomley
2009-01-25  4:22                   ` Mike Snitzer
2009-01-22 14:56       ` James Bottomley

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=1227485085.25499.5.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=Babu.Moger@lsi.com \
    --cc=andmike@linux.vnet.ibm.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sekharan@us.ibm.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