From: Gerald Schaefer <geraldsc@de.ibm.com>
Subject: zfcp: Update parameter name in LUN limit kernel message
Patch-mainline: no
References: bnc#713134

Symptom: Max_report_luns=0 parameter has no effect in certain cases.
Problem: The order of scsi_host capability registration can lead to
             auto lun scanning being active despite max_report_luns=0.
Solution: Document new zfcp_allow_lun scan parameter that was introduced
             to reliably suppress auto lun scanning.
Problem-id: 74714

Signed-off-by: Gerald Schaefer <geraldsc@de.ibm.com>
Acked-by: Torsten Duwe <duwe@suse.de>

---
 Documentation/kmsg/s390/zfcp |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

--- a/Documentation/kmsg/s390/zfcp
+++ b/Documentation/kmsg/s390/zfcp
@@ -724,7 +724,8 @@
  * host connections on the storage systems. Ensure that the zoning and
  * host connections only allow access to the required LUNs. As a
  * workaround, disable the automatic LUN scanning by setting the
- * max_report_luns parameter to 0.
+ * zfcp.allow_lun_scan kernel parameter or the allow_lun_scan module
+ * parameter to 0.
  */
 
 /*?
