---

yaml
---
r: 136223
b: refs/heads/master
c: 5ef0741
h: refs/heads/master
i:
  136221: 34e4801
  136219: 0193fd7
  136215: db3177f
  136207: 966f430
  136191: f749f04
v: v3

[refs]

@@ -1,2 +1,2 @@
 ---
-refs/heads/master: 0762a4824d6c6f8eb5d2646dfda95581d99afaa5
+refs/heads/master: 5ef074161b5bcd84acfe19f0ecd72b74765d8770

trunk/drivers/scsi/Kconfig

@@ -224,14 +224,15 @@ config SCSI_LOGGING
 	  can enable logging by saying Y to "/proc file system support" and
 	  "Sysctl support" below and executing the command
 
-	  echo "scsi log token [level]" > /proc/scsi/scsi
+	  echo <bitmask> > /proc/sys/dev/scsi/logging_level
 
-	  at boot time after the /proc file system has been mounted.
+	  where <bitmask> is a four byte value representing the logging type
+	  and logging level for each type of logging selected.
 
-	  There are a number of things that can be used for 'token' (you can
-	  find them in the source: <file:drivers/scsi/scsi.c>), and this
-	  allows you to select the types of information you want, and the
-	  level allows you to select the level of verbosity.
+	  There are a number of logging types and you can find them in the
+	  source at <file:drivers/scsi/scsi_logging.h>. The logging levels
+	  are also described in that file and they determine the verbosity of
+	  the logging for each logging type.
 
 	  If you say N here, it may be harder to track down some types of SCSI
 	  problems. If you say Y here your kernel will be somewhat larger, but