public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Chandra Seetharaman <sekharan@us.ibm.com>
To: Hannes Reinecke <hare@suse.de>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	dm-devel <dm-devel@redhat.com>
Subject: Re: [PATCH 0/7] scsi_dh framework update
Date: Wed, 14 May 2008 19:45:40 -0700	[thread overview]
Message-ID: <1210819540.21974.250.camel@chandra-ubuntu> (raw)
In-Reply-To: <482AFA62.2000506@suse.de>

Hi Hannes,

Thanks for the clean up and the new features. I have reviewed the code
but hasn't tested it. Comments follow.

BTW, checkpatch.pl generates warnings for patches 1 thru 5.

regards,

chandra
On Wed, 2008-05-14 at 16:42 +0200, Hannes Reinecke wrote:
> Hi James,
> 
> this is a repost of my patchset to update the scsi_dh infrastructure.
> 
> It's based on the current scsi-misc tree.
> 
> Main features of the patchset are:
> - Use a single callback for the notifier chain
> - Merge all device maps into a single list,
>   which will be scanned by a generic function
> - Add a sysfs attribute 'dh_state' for each sdev
> - Add a generic SPC-3 ALUA device handler
> - Update device handlers to check if the
>   device actually supports this handler.
>   When attaching manually we are able to attach
>   to basically any device, so we have to make sure
>   that the device handler is actually supported.
> - Manually attach a device when a hardware handler
>   is specified; this allows multipath to override
>   the built-in hardware table.
> 
> As per usual, comment etc are welcome.
> 
> Cheers,
> 
> Hannes


      reply	other threads:[~2008-05-15  2:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 14:42 [PATCH 0/7] scsi_dh framework update Hannes Reinecke
2008-05-15  2:45 ` Chandra Seetharaman [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=1210819540.21974.250.camel@chandra-ubuntu \
    --to=sekharan@us.ibm.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=dm-devel@redhat.com \
    --cc=hare@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    /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