From: Hannes Reinecke <hare@suse.de>
To: James Bottomley <jbottomley@parallels.com>
Cc: linux-scsi@vger.kernel.org, Hannes Reinecke <hare@suse.de>
Subject: [PATCH 0/5] Cleanup struct Scsi_Host
Date: Mon, 6 May 2013 09:20:36 +0200 [thread overview]
Message-ID: <1367824841-47767-1-git-send-email-hare@suse.de> (raw)
The 'Scsi_Host' structure has two fields 'resetting' and
'last_reset' which are basically unused. There are only
4 drivers referencing 'last_reset' (dpt_i2o, tmscsim, dc395, and advansys),
and only dpt_i2o makes usage of both fields.
However, dpt_i2o does _not_ require a delay after reset,
so even there the usage is questionable.
So move the 'last_reset' field into the internal host
structure where needed and remove both fields from
struct Scsi_Host.
Hannes Reinecke (5):
scsi: remove 'resetting' field from struct Scsi_Host
tmscsim: Move 'last_reset' into host structure
dc395: Move 'last_reset' into internal host structure
advansys: Remove references to 'last_reset'
scsi: Remove 'last_reset' for struct Scsi_Host
drivers/scsi/advansys.c | 8 ++++----
drivers/scsi/dc395x.c | 24 +++++++++++++-----------
drivers/scsi/dpt_i2o.c | 22 +++-------------------
drivers/scsi/scsi.c | 25 +------------------------
drivers/scsi/tmscsim.c | 12 ++++++------
drivers/scsi/tmscsim.h | 1 +
include/scsi/scsi_host.h | 4 +---
7 files changed, 29 insertions(+), 67 deletions(-)
--
1.7.12.4
next reply other threads:[~2013-05-06 7:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 7:20 Hannes Reinecke [this message]
2013-05-06 7:20 ` [PATCH 1/5] scsi: remove 'resetting' field from struct Scsi_Host Hannes Reinecke
2013-05-06 7:20 ` [PATCH 2/5] tmscsim: Move 'last_reset' into host structure Hannes Reinecke
2013-05-06 7:20 ` [PATCH 3/5] dc395: Move 'last_reset' into internal " Hannes Reinecke
2013-05-06 7:20 ` [PATCH 4/5] advansys: Remove references to 'last_reset' Hannes Reinecke
2013-05-06 7:20 ` [PATCH 5/5] scsi: Remove 'last_reset' for struct Scsi_Host Hannes Reinecke
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=1367824841-47767-1-git-send-email-hare@suse.de \
--to=hare@suse.de \
--cc=jbottomley@parallels.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox