From: Hannes Reinecke <hare@suse.de>
To: Mike Snitzer <snitzer@redhat.com>
Cc: linux-scsi@vger.kernel.org, agk@redhat.com,
babu.moger@netapp.com, sekharan@us.ibm.com, dm-devel@redhat.com
Subject: Re: [PATCH v4 2/5] scsi_dh: add scsi_dh_attached_handler_name
Date: Fri, 08 Jun 2012 17:03:44 +0200 [thread overview]
Message-ID: <4FD21450.9020103@suse.de> (raw)
In-Reply-To: <20120510213112.GA7374@redhat.com>
On 05/10/2012 11:31 PM, Mike Snitzer wrote:
> Introduce scsi_dh_attached_handler_name() to retrieve the name of the
> scsi_dh that is attached to the scsi_device associated with the provided
> request queue. Returns NULL if a scsi_dh is not attached.
>
> Also, fix scsi_dh_{attach,detach} function header comments to document
> @q rather than @sdev.
>
> Signed-off-by: Mike Snitzer <snitzer@redhat.com>
> Tested-by: Babu Moger <babu.moger@netapp.com>
> Cc: Hannes Reinecke <hare@suse.de>
Acked-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, 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
prev parent reply other threads:[~2012-06-08 15:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 1:12 [PATCH v3 2/5] scsi_dh: add scsi_dh_attached_handler_name Mike Snitzer
2012-05-10 6:55 ` Christoph Hellwig
2012-05-10 14:10 ` Mike Snitzer
2012-05-10 18:14 ` Moger, Babu
2012-05-10 20:26 ` Moger, Babu
2012-05-10 21:31 ` [PATCH v4 " Mike Snitzer
2012-05-17 21:12 ` Chandra Seetharaman
2012-05-17 21:23 ` Mike Snitzer
2012-05-17 22:57 ` Chandra Seetharaman
2012-05-17 22:58 ` Chandra Seetharaman
2012-05-21 18:45 ` Mike Snitzer
2012-06-08 15:03 ` Hannes Reinecke [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=4FD21450.9020103@suse.de \
--to=hare@suse.de \
--cc=agk@redhat.com \
--cc=babu.moger@netapp.com \
--cc=dm-devel@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=sekharan@us.ibm.com \
--cc=snitzer@redhat.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).