Re: [PATCH 0/2][RESEND] scsi_transport_fc: LUN masking

2016-03-01 Thread Hannes Reinecke
On 03/02/2016 03:54 AM, Ewan Milne wrote: > On Tue, 2016-02-23 at 18:21 +0800, Hannes Reinecke wrote: >> On 02/22/2016 07:39 PM, Seymour, Shane M wrote: >>> Hi Hannes, >>> >>> How do you know that a request for an async scan is complete (I'm assuming >>> that you get add or change udev events)?

Re: [PATCH 0/2][RESEND] scsi_transport_fc: LUN masking

2016-03-01 Thread Ewan Milne
On Tue, 2016-02-23 at 18:21 +0800, Hannes Reinecke wrote: > On 02/22/2016 07:39 PM, Seymour, Shane M wrote: > > Hi Hannes, > > > > How do you know that a request for an async scan is complete (I'm assuming > > that you get > > add or change udev events)? Assuming that someone has manually

RE: [PATCH 0/2][RESEND] scsi_transport_fc: LUN masking

2016-02-23 Thread Seymour, Shane M
> But this has nothing to do with the patchset, right? Correct. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH 0/2][RESEND] scsi_transport_fc: LUN masking

2016-02-23 Thread Hannes Reinecke
On 02/22/2016 07:39 PM, Seymour, Shane M wrote: > Hi Hannes, > > How do you know that a request for an async scan is complete (I'm assuming > that you get > add or change udev events)? Assuming that someone has manually started a scan > on something > (e.g. some newly presented devices after

RE: [PATCH 0/2][RESEND] scsi_transport_fc: LUN masking

2016-02-22 Thread Seymour, Shane M
Hi Hannes, How do you know that a request for an async scan is complete (I'm assuming that you get add or change udev events)? Assuming that someone has manually started a scan on something (e.g. some newly presented devices after boot) and all scans are going to be async how do you when it is