From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: KY Srinivasan <kys@microsoft.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"ohering@suse.com" <ohering@suse.com>,
"jbottomley@parallels.com" <jbottomley@parallels.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
"hare@suse.de" <hare@suse.de>,
"apw@canonical.com" <apw@canonical.com>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>
Subject: Re: [PATCH 1/1] scsi: storvsc: Support manual scan of FC hosts on Hyper-V
Date: Wed, 16 Mar 2016 18:34:45 -0400 [thread overview]
Message-ID: <yq14mc6dpbu.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <SN2PR03MB21425F84DAC997491DD4C2ACA0890@SN2PR03MB2142.namprd03.prod.outlook.com> (KY Srinivasan's message of "Tue, 15 Mar 2016 23:01:03 +0000")
>>>>> "KY" == KY Srinivasan <kys@microsoft.com> writes:
KY> How would I get the sysfs files under fc_host if I don't use the FC
KY> transport. The customer scripts expect these sysfs files.
Right, but I was interested in finding out why they need those
files. And whether an alternative to the FC transport would be a better
solution.
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: KY Srinivasan <kys@microsoft.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@infradead.org>,
"gregkh\@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel\@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"ohering\@suse.com" <ohering@suse.com>,
"jbottomley\@parallels.com" <jbottomley@parallels.com>,
"linux-scsi\@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"apw\@canonical.com" <apw@canonical.com>,
"vkuznets\@redhat.com" <vkuznets@redhat.com>,
"jasowang\@redhat.com" <jasowang@redhat.com>,
"hare\@suse.de" <hare@suse.de>
Subject: Re: [PATCH 1/1] scsi: storvsc: Support manual scan of FC hosts on Hyper-V
Date: Wed, 16 Mar 2016 18:34:45 -0400 [thread overview]
Message-ID: <yq14mc6dpbu.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <SN2PR03MB21425F84DAC997491DD4C2ACA0890@SN2PR03MB2142.namprd03.prod.outlook.com> (KY Srinivasan's message of "Tue, 15 Mar 2016 23:01:03 +0000")
>>>>> "KY" == KY Srinivasan <kys@microsoft.com> writes:
KY> How would I get the sysfs files under fc_host if I don't use the FC
KY> transport. The customer scripts expect these sysfs files.
Right, but I was interested in finding out why they need those
files. And whether an alternative to the FC transport would be a better
solution.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2016-03-16 22:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-12 21:52 [PATCH 1/1] scsi: storvsc: Support manual scan of FC hosts on Hyper-V K. Y. Srinivasan
2016-03-12 21:52 ` K. Y. Srinivasan
2016-03-15 13:40 ` Christoph Hellwig
2016-03-15 13:40 ` Christoph Hellwig
2016-03-15 14:27 ` KY Srinivasan
2016-03-15 14:27 ` KY Srinivasan
2016-03-15 21:25 ` Martin K. Petersen
2016-03-15 21:25 ` Martin K. Petersen
2016-03-15 23:01 ` KY Srinivasan
2016-03-16 22:34 ` Martin K. Petersen [this message]
2016-03-16 22:34 ` Martin K. Petersen
2016-03-16 23:07 ` James Bottomley
2016-03-16 23:07 ` James Bottomley
2016-03-16 23:15 ` KY Srinivasan
2016-03-16 23:15 ` KY Srinivasan
2016-03-16 23:40 ` James Bottomley
2016-03-16 23:40 ` James Bottomley
2016-03-17 0:01 ` KY Srinivasan
2016-03-17 0:01 ` KY Srinivasan
2016-03-18 22:41 ` James Bottomley
2016-03-18 22:41 ` James Bottomley
2016-03-18 22:42 ` [PATCH 2/2] storvsc_drv: make use of the lightweight FC transport class James Bottomley
2016-03-18 22:42 ` James Bottomley
2016-03-20 18:58 ` [PATCH 1/1] scsi: storvsc: Support manual scan of FC hosts on Hyper-V KY Srinivasan
2016-03-20 18:58 ` KY Srinivasan
2016-03-22 20:10 ` KY Srinivasan
2016-03-30 6:39 ` KY Srinivasan
2016-03-30 6:39 ` KY Srinivasan
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=yq14mc6dpbu.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=jasowang@redhat.com \
--cc=jbottomley@parallels.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ohering@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.