public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
	KY Srinivasan <kys@microsoft.com>
Cc: 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 16:07:46 -0700	[thread overview]
Message-ID: <1458169666.4793.62.camel@HansenPartnership.com> (raw)
In-Reply-To: <yq14mc6dpbu.fsf@sermon.lab.mkp.net>

On Wed, 2016-03-16 at 18:34 -0400, Martin K. Petersen wrote:
> > > > > > "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.

If it's just the wwn file (or a set of other values), we might be able
to separate that bit out of the FC transport class so you can use it
independently ... do you have a full list of the files being used?

Thanks,

James

  reply	other threads:[~2016-03-16 23:07 UTC|newest]

Thread overview: 15+ 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-15 13:40 ` Christoph Hellwig
2016-03-15 14:27   ` KY Srinivasan
2016-03-15 21:25     ` Martin K. Petersen
2016-03-15 23:01       ` KY Srinivasan
2016-03-16 22:34         ` Martin K. Petersen
2016-03-16 23:07           ` James Bottomley [this message]
2016-03-16 23:15             ` KY Srinivasan
2016-03-16 23:40               ` James Bottomley
2016-03-17  0:01                 ` KY Srinivasan
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-20 18:58                     ` [PATCH 1/1] scsi: storvsc: Support manual scan of FC hosts on Hyper-V KY Srinivasan
2016-03-22 20:10                       ` 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=1458169666.4793.62.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.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=martin.petersen@oracle.com \
    --cc=ohering@suse.com \
    --cc=vkuznets@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