From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Martin K. Petersen" Subject: Re: [PATCH 1/1] scsi: storvsc: Support manual scan of FC hosts on Hyper-V Date: Tue, 15 Mar 2016 17:25:02 -0400 Message-ID: References: <1457819568-6586-1-git-send-email-kys@microsoft.com> <20160315134009.GA3595@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: (KY Srinivasan's message of "Tue, 15 Mar 2016 14:27:53 +0000") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: driverdev-devel-bounces@linuxdriverproject.org Sender: "devel" To: KY Srinivasan Cc: "martin.petersen@oracle.com" , "linux-scsi@vger.kernel.org" , "gregkh@linuxfoundation.org" , "jasowang@redhat.com" , "ohering@suse.com" , "jbottomley@parallels.com" , "linux-kernel@vger.kernel.org" , Christoph Hellwig , "hare@suse.de" , "apw@canonical.com" , "devel@linuxdriverproject.org" List-Id: linux-scsi@vger.kernel.org >>>>> "KY" == KY Srinivasan writes: KY> Till recently I had not. However, we do support publishing wwn in KY> the guest and some customers wanted this. That is the reason I am KY> attaching FC transport and working through the issues. With this KY> change, I now have wwn names published in the guest and I can also KY> issue manual scan. Why does it have to look like FC? Will a device identification VPD page not do the trick? -- Martin K. Petersen Oracle Linux Engineering