Re: [PATCH as470] Add a NOREPORTLUN blacklist flag

2005-02-28 Thread James Bottomley
On Sun, 2005-02-20 at 22:44 -0500, Alan Stern wrote: James, please withdraw the patch above. Actually, I already have this in the tree. Could you just do an incremental to remove the blacklist line since I think the IBM people still want their shark fix? Thanks, James - To unsubscribe from

Re: [PATCH as470] Add a NOREPORTLUN blacklist flag

2005-02-21 Thread Patrick Mansfield
On Sun, Feb 20, 2005 at 10:47:09PM -0800, Matthew Dharm wrote: On Sun, Feb 20, 2005 at 10:44:21PM -0500, Alan Stern wrote: Matt, it looks like the best way to solve this problem is to go back to the old strategy of always setting the SCSI revision to 2 (no matter what it might actually

Re: [PATCH as470] Add a NOREPORTLUN blacklist flag

2005-02-21 Thread Alan Stern
On Sun, 20 Feb 2005, Matthew Dharm wrote: Matt, it looks like the best way to solve this problem is to go back to the old strategy of always setting the SCSI revision to 2 (no matter what it might actually be), at least for Direct Access devices. That would suppress the REPORT_LUNS

Re: [PATCH as470] Add a NOREPORTLUN blacklist flag

2005-02-20 Thread Sergey Vlasov
On Thu, 17 Feb 2005 17:31:04 -0500 (EST) Alan Stern wrote: James: This patch adds a NOREPORTLUN blacklist flag for a disk made by WDC (Winchester?). The drive's firmware crashes when it receives REPORT_LUNS, even though it claims to be SCSI rev 04. Alan Stern Signed-off-by:

[PATCH as470] Add a NOREPORTLUN blacklist flag

2005-02-17 Thread Alan Stern
James: This patch adds a NOREPORTLUN blacklist flag for a disk made by WDC (Winchester?). The drive's firmware crashes when it receives REPORT_LUNS, even though it claims to be SCSI rev 04. Alan Stern Signed-off-by: Alan Stern [EMAIL PROTECTED] = drivers/scsi/scsi_devinfo.c 1.14 vs