From 8857274edbf3d708806fcacbfa3e8e196bd69ae1 Mon Sep 17 00:00:00 2001 From: Bart Van Assche Date: Sun, 7 Apr 2019 18:19:12 +0000 Subject: [PATCH] qla2x00t-32gbit, target: Make a comment more clear git-svn-id: http://svn.code.sf.net/p/scst/svn/trunk@8170 d57e44dd-8a1f-0410-8b47-8ef2f437770f --- qla2x00t-32gbit/qla2x00-target/scst_qla2xxx.c | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-) diff --git a/qla2x00t-32gbit/qla2x00-target/scst_qla2xxx.c b/qla2x00t-32gbit/qla2x00-target/scst_qla2xxx.c index 9db2e24d0..82f08ee91 100644 --- a/qla2x00t-32gbit/qla2x00-target/scst_qla2xxx.c +++ b/qla2x00t-32gbit/qla2x00-target/scst_qla2xxx.c @@ -26,17 +26,15 @@ */ /* - * This interface driver sits at the three way nexus between the SCST - * driver core, the Cavium in-kernel target driver and the in-kernel - * SCSI target driver. It does not require that the in-kernel SCSI - * target driver be enabled but it does make use of various structures - * defined by the in-kernel driver in order to facilitate communications - * between this interface driver and the low level target driver. + * This driver is an interface between the SCST core and the Cavium target + * code (qla_target.c). It uses the LIO se_session and se_cmd data structures + * to exchange information between this interface driver and the qla2xxx + * driver. * * This interface driver relies heavily upon hardware and mutex locking - * supplied by the low level driver. The primary exception to this - * is the statically scoped sqa_mutex locks which provides exclusion - * locking between target registraiton and module unload. + * supplied by the qla2xxx driver. The primary exception to this is the + * statically scoped sqa_mutex locks which provides exclusion locking between + * target registration and module unload. */ #define EXCLUDED 0