Re: [PATCH 1 18/25] External array LUNs must use target and lun numbers assigned by the

2015-10-30 Thread Hannes Reinecke
On 10/28/2015 11:06 PM, Don Brace wrote: > From: Scott Teel > > external array. So the driver must treat these differently from > local LUNs when assigning lun/target. > Please fixup the description; looks like it has been incorrectly broken up during git commit. > LUN's

Re: [PATCH 1 18/25] External array LUNs must use target and lun numbers assigned by the

2015-10-30 Thread Tomas Henzl
On 28.10.2015 23:06, Don Brace wrote: > From: Scott Teel > > external array. So the driver must treat these differently from > local LUNs when assigning lun/target. > > LUN's 'model' field has been used to detect Lun types that need > special treatment, but the desire is to

Re: [PATCH 1 18/25] External array LUNs must use target and lun numbers assigned by the

2015-10-29 Thread Matthew R. Ochs
> On Oct 28, 2015, at 5:06 PM, Don Brace wrote: > > From: Scott Teel > > external array. So the driver must treat these differently from > local LUNs when assigning lun/target. > > LUN's 'model' field has been used to detect Lun types that need >

[PATCH 1 18/25] External array LUNs must use target and lun numbers assigned by the

2015-10-28 Thread Don Brace
From: Scott Teel external array. So the driver must treat these differently from local LUNs when assigning lun/target. LUN's 'model' field has been used to detect Lun types that need special treatment, but the desire is to eliminate the need to reference specific array