linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: sekharan@linux.vnet.ibm.com
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	Kay Sievers <kay.sievers@vrfy.org>,
	linux-scsi@vger.kernel.org, michaelc@cs.wisc.edu,
	Peter Jones <pjones@redhat.com>
Subject: Re: [PATCH 1/3] scsi_dh: Add modalias support for SCSI targets
Date: Thu, 16 Apr 2009 17:18:38 +0200	[thread overview]
Message-ID: <49E74C4E.8030407@suse.de> (raw)
In-Reply-To: <1239832363.1196.5.camel@chandra-ubuntu>

Chandra Seetharaman wrote:
> Hi James,
> 
> Are your concerns answered ?
> 
> Hannes, Kay,
> 
> Is the description related to bus notify BIND DEVICE issue clear now ?
> 
> Please respond :)
> 
Yes, issue is clearer now.

Basically this is another instance where multi-driver binding would make
a difference. Using the 'notifier_chain' approach is basically doing
the very same thing whilst _not_ using driver core binding.

So from that point of view:

Acked-by: Hannes Reinecke <hare@suse.de>

However, I would really like to see it merged with my ALUA update
for scsi_dh; for ALUA matching on the vendor/product tuple is really
quite pointless and we should be using the 'TPGS' setting in
the inquiry data.

Trading your ack for mine :-)

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-04-16 15:18 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18  1:36 [PATCH 0/3] scsi_dh: Make scsi device handler modules automatically inserted Chandra Seetharaman
2009-03-18  1:36 ` [PATCH 1/3] scsi_dh: Add modalias support for SCSI targets Chandra Seetharaman
2009-03-18 13:44   ` Konrad Rzeszutek
2009-03-18 14:02     ` James Bottomley
2009-03-18 14:36       ` Konrad Rzeszutek
2009-03-18 18:30   ` Kay Sievers
2009-03-18 19:18     ` Chandra Seetharaman
2009-03-19 18:54       ` Chandra Seetharaman
2009-03-20 18:24         ` Peter Jones
2009-03-23 22:13           ` Chandra Seetharaman
2009-04-03 22:43             ` Chandra Seetharaman
2009-04-07 20:59               ` James Bottomley
2009-04-07 23:41                 ` Chandra Seetharaman
2009-04-08 15:08                 ` Peter Jones
2009-04-15 21:52                   ` Chandra Seetharaman
2009-04-16 15:18                     ` Hannes Reinecke [this message]
2009-04-07 23:22               ` Hannes Reinecke
2009-04-07 23:50                 ` Chandra Seetharaman
2009-04-08  5:15                   ` Kay Sievers
2009-04-08 19:13                     ` Chandra Seetharaman
2009-03-18 18:47   ` James Bottomley
2009-03-18 19:12     ` Chandra Seetharaman
2009-03-18 20:09       ` James Bottomley
2009-03-18 20:24         ` Kay Sievers
2009-03-18 20:26           ` James Bottomley
2009-03-18 20:59         ` Chandra Seetharaman
2009-03-20 17:41         ` Peter Jones
2009-03-18  1:36 ` [PATCH 2/3] scsi_dh: Change scsi device handler modules to utilize modalias Chandra Seetharaman
2009-03-18 13:46   ` Konrad Rzeszutek
2009-03-18 15:43     ` Stefan Richter
2009-03-18 17:25       ` Chandra Seetharaman
2009-03-18 17:50         ` Stefan Richter
2009-03-18 18:18           ` Kay Sievers
2009-03-18 19:44             ` Stefan Richter
2009-03-18 18:50           ` Chandra Seetharaman
2009-03-18 19:46             ` Stefan Richter
2009-03-18  1:36 ` [PATCH 3/3] scsi_dh: Workaround a race condition in module insertion Chandra Seetharaman
2009-03-18 11:31 ` [PATCH 0/3] scsi_dh: Make scsi device handler modules automatically inserted Hannes Reinecke
  -- strict thread matches above, loose matches on Subject: below --
2009-04-27 18:06 Chandra Seetharaman
2009-04-27 18:06 ` [PATCH 1/3] scsi_dh: Add modalias support for SCSI targets Chandra Seetharaman

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=49E74C4E.8030407@suse.de \
    --to=hare@suse.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=pjones@redhat.com \
    --cc=sekharan@linux.vnet.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;
as well as URLs for NNTP newsgroup(s).