From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux-scsi@vger.kernel.org
Cc: linux1394-devel@lists.sourceforge.net
Subject: [RFC PATCH] sbp2: remove manipulation of inquiry response
Date: Sat, 8 Apr 2006 20:45:24 +0200 (CEST) [thread overview]
Message-ID: <tkrat.d3b4470a9a767dd4@s5r6.in-berlin.de> (raw)
This code became ineffective a few Linux releases ago and is
apparently not required anyway.
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Index: linux-2.6.17-rc1/drivers/ieee1394/sbp2.c
===================================================================
--- linux-2.6.17-rc1.orig/drivers/ieee1394/sbp2.c 2006-04-08 09:43:33.000000000 +0200
+++ linux-2.6.17-rc1/drivers/ieee1394/sbp2.c 2006-04-08 20:40:00.000000000 +0200
@@ -2079,33 +2079,6 @@ static unsigned int sbp2_status_to_sense
}
/*
- * This function is called after a command is completed, in order to do any necessary SBP-2
- * response data translations for the SCSI stack
- */
-static void sbp2_check_sbp2_response(struct scsi_id_instance_data *scsi_id,
- struct scsi_cmnd *SCpnt)
-{
- u8 *scsi_buf = SCpnt->request_buffer;
-
- SBP2_DEBUG_ENTER();
-
- if (SCpnt->cmnd[0] == INQUIRY && (SCpnt->cmnd[1] & 3) == 0) {
- /*
- * Make sure data length is ok. Minimum length is 36 bytes
- */
- if (scsi_buf[4] == 0) {
- scsi_buf[4] = 36 - 5;
- }
-
- /*
- * Fix ansi revision and response data format
- */
- scsi_buf[2] |= 2;
- scsi_buf[3] = (scsi_buf[3] & 0xf0) | 2;
- }
-}
-
-/*
* This function deals with status writes from the SBP-2 device
*/
static int sbp2_handle_status_write(struct hpsb_host *host, int nodeid, int destid,
@@ -2444,13 +2417,6 @@ static void sbp2scsi_complete_command(st
}
/*
- * Take care of any sbp2 response data mucking here (RBC stuff, etc.)
- */
- if (SCpnt->result == DID_OK << 16) {
- sbp2_check_sbp2_response(scsi_id, SCpnt);
- }
-
- /*
* If a bus reset is in progress and there was an error, complete
* the command as busy so that it will get retried.
*/
Index: linux-2.6.17-rc1/drivers/ieee1394/sbp2.h
===================================================================
--- linux-2.6.17-rc1.orig/drivers/ieee1394/sbp2.h 2006-04-08 09:43:32.000000000 +0200
+++ linux-2.6.17-rc1/drivers/ieee1394/sbp2.h 2006-04-08 20:40:00.000000000 +0200
@@ -394,9 +394,8 @@ static int sbp2_link_orb_command(struct
static int sbp2_send_command(struct scsi_id_instance_data *scsi_id,
struct scsi_cmnd *SCpnt,
void (*done)(struct scsi_cmnd *));
-static unsigned int sbp2_status_to_sense_data(unchar *sbp2_status, unchar *sense_data);
-static void sbp2_check_sbp2_response(struct scsi_id_instance_data *scsi_id,
- struct scsi_cmnd *SCpnt);
+static unsigned int sbp2_status_to_sense_data(unchar *sbp2_status,
+ unchar *sense_data);
static void sbp2_parse_unit_directory(struct scsi_id_instance_data *scsi_id,
struct unit_directory *ud);
static int sbp2_set_busy_timeout(struct scsi_id_instance_data *scsi_id);
next reply other threads:[~2006-04-08 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-08 18:45 Stefan Richter [this message]
2006-04-08 18:55 ` [RFC PATCH] sbp2: remove manipulation of inquiry response Stefan Richter
2006-04-09 11:08 ` Jeff Garzik
2006-04-09 11:19 ` Christoph Hellwig
2006-04-09 12:47 ` Stefan Richter
2006-04-18 9:41 ` Jody McIntyre
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=tkrat.d3b4470a9a767dd4@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux-scsi@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox