linux-kernel - [PATCH] [SCSI] Remove reference to scsi_wait_scan module in SCSI_SCAN

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Mon, 28 Jul 2014 17:12:31 -0700
From:	Yannick Brosseau <scientist@...com>
To:	<JBottomley@...allels.com>, <linux-scsi@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
CC:	<kernel-team@...com>, Yannick Brosseau <scientist@...com>
Subject: [PATCH] [SCSI] Remove reference to scsi_wait_scan module in SCSI_SCAN_ASYNC doc

The module was removed in c6072609d9bb91ff54aee3ef29304bd5b4fc88aae
   Author: James Bottomley <JBottomley@...allels.com>
   Date:   Sun May 27 10:13:46 2012 +0100

    [SCSI] Remove scsi_wait_scan module

Signed-off-by: Yannick Brosseau <scientist@...com>
---
 drivers/scsi/Kconfig | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig
index baca589..6e126d1 100644
--- a/drivers/scsi/Kconfig
+++ b/drivers/scsi/Kconfig
@@ -255,8 +255,7 @@ config SCSI_SCAN_ASYNC
 
 	  If you have built SCSI as modules, enabling this option can
 	  be a problem as the devices may not have been found by the
-	  time your system expects them to have been.  You can load the
-	  scsi_wait_scan module to ensure that all scans have completed.
+	  time your system expects them to have been.
 	  If you build your SCSI drivers into the kernel, then everything
 	  will work fine if you say Y here.
 
-- 
2.0.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/