From: Douglas Gilbert <dougg@torque.net>
To: SCSI Mailing List <linux-scsi@vger.kernel.org>
Cc: James.Bottomley@SteelEye.com
Subject: [PATCH] scsi_debug dsense lk2.6.11-rc1
Date: Thu, 13 Jan 2005 18:49:02 +1000 [thread overview]
Message-ID: <41E635FE.20100@torque.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
The dsense switch in the scsi_debug driver selects
whether fixed (default) or descriptor format sense
data is returned when an error/warning occurs. Due
to an oversight dsense was not sysfs visible.
James, will the new generic device transport class be
useful for the scsi_debug driver. At the moment it uses
a "pseudo" device and bus type. When I tried to replicate
that structure in another virtual driver (for a SES target)
I found that the two drivers didn't play well together.
Changelog:
- make dsense visible to sysfs
Signed-off-by: Douglas Gilbert <dougg@torque.net>
[-- Attachment #2: sdebug2611rc1.diff --]
[-- Type: text/x-patch, Size: 1795 bytes --]
--- linux/drivers/scsi/scsi_debug.c 2005-01-13 14:41:44.000000000 +1000
+++ linux/drivers/scsi/scsi_debug.c2611rc1dpg 2005-01-13 14:34:43.000000000 +1000
@@ -11,7 +11,7 @@
* (or disk like devices) sharing a common amount of RAM
*
*
- * For documentation see http://www.torque.net/sg/sdebug25.html
+ * For documentation see http://www.torque.net/sg/sdebug26.html
*
* D. Gilbert (dpg) work for Magneto-Optical device test [20010421]
* dpg: work for devfs large number of disks [20010809]
@@ -56,7 +56,7 @@
#include "scsi_debug.h"
#define SCSI_DEBUG_VERSION "1.75"
-static const char * scsi_debug_version_date = "20041023";
+static const char * scsi_debug_version_date = "20050113";
/* Additional Sense Code (ASC) used */
#define NO_ADDED_SENSE 0x0
@@ -1675,6 +1675,7 @@
driver_create_file(&sdebug_driverfs_driver, &driver_attr_add_host);
driver_create_file(&sdebug_driverfs_driver, &driver_attr_delay);
driver_create_file(&sdebug_driverfs_driver, &driver_attr_dev_size_mb);
+ driver_create_file(&sdebug_driverfs_driver, &driver_attr_dsense);
driver_create_file(&sdebug_driverfs_driver, &driver_attr_every_nth);
driver_create_file(&sdebug_driverfs_driver, &driver_attr_max_luns);
driver_create_file(&sdebug_driverfs_driver, &driver_attr_num_tgts);
@@ -1693,6 +1694,7 @@
driver_remove_file(&sdebug_driverfs_driver, &driver_attr_num_tgts);
driver_remove_file(&sdebug_driverfs_driver, &driver_attr_max_luns);
driver_remove_file(&sdebug_driverfs_driver, &driver_attr_every_nth);
+ driver_remove_file(&sdebug_driverfs_driver, &driver_attr_dsense);
driver_remove_file(&sdebug_driverfs_driver, &driver_attr_dev_size_mb);
driver_remove_file(&sdebug_driverfs_driver, &driver_attr_delay);
driver_remove_file(&sdebug_driverfs_driver, &driver_attr_add_host);
reply other threads:[~2005-01-13 8:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41E635FE.20100@torque.net \
--to=dougg@torque.net \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.