@infradead.org; linux-scsi@vger.kernel.org
> Subject: Re: scanning for LUNs
>
> On 04/04/2013 07:12 PM, KY Srinivasan wrote:
> >
> >
> >> -Original Message-
> >> From: James Bottomley [mailto:jbottom...@parallels.com]
> >> Sent:
linux-ker...@vger.kernel.org;
>> de...@linuxdriverproject.org; oher...@suse.com; h...@infradead.org; linux-
>> s...@vger.kernel.org
>> Subject: Re: scanning for LUNs
>>
>> On Thu, 2013-04-04 at 08:12 -0700, K. Y. Srinivasan wrote:
>>> Here is the code snippet for scan
ad.org; linux-
> s...@vger.kernel.org
> Subject: Re: scanning for LUNs
>
> On Thu, 2013-04-04 at 08:12 -0700, K. Y. Srinivasan wrote:
> > Here is the code snippet for scanning LUNS (drivers/scsi/scsi_scan.c in
> > function
> > __scsi_scan_target()):
> >
>
On Thu, 2013-04-04 at 08:12 -0700, K. Y. Srinivasan wrote:
> Here is the code snippet for scanning LUNS (drivers/scsi/scsi_scan.c in
> function
> __scsi_scan_target()):
>
> /*
> * Scan LUN 0, if there is some response, scan further. Ideally, we
> * would not configure L
Here is the code snippet for scanning LUNS (drivers/scsi/scsi_scan.c in
function
__scsi_scan_target()):
/*
* Scan LUN 0, if there is some response, scan further. Ideally, we
* would not configure LUN 0 until all LUNs are scanned.
*/
res = scsi_probe_and
5 matches
Mail list logo