From: Hannes Reinecke <hare@suse.de>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
Johannes Thumshirn <jth@kernel.org>, Jens Axboe <axboe@kernel.dk>,
James Bottomley <james.bottomley@hansenpartnership.com>,
linux-scsi@vger.kernel.org, Hannes Reinecke <hare@suse.de>
Subject: [PATCHv2 0/5] Deprecate DAC960 driver
Date: Fri, 19 Jan 2018 16:11:08 +0100 [thread overview]
Message-ID: <20180119151113.80768-1-hare@suse.de> (raw)
Hi all,
as we're trying to get rid of the remaining request_fn drivers here's
a patchset to move the DAC960 driver to the SCSI stack.
As per request from hch I've split up the driver into two new SCSI
drivers called 'myrb' and 'myrs'.
The 'myrb' driver only supports the earlier (V1) firmware interface, which
doesn't have a SCSI interface for the logical drives; for those I've added
a (pretty rudimentary, admittedly) SCSI translation for them.
The 'myrs' driver supports the newer (V2) firmware interface, which is
SCSI based and doesn't need the translation layer.
And the weird proc interface from DAC960 has been converted to sysfs attributes.
Tested with eXtremeRAID 1100 (for V1 Firmware) and Mylex AcceleRAID 170
(for V2 Firmware).
Changes to v1:
- Split into two drivers
- Improve scanning for V1 firmware interface
Hannes Reinecke (5):
raid_class: Add 'JBOD' RAID level
scsi: Add VENDOR_SPECIFIC sense code definitions
myrb: Add Mylex RAID controller (block interface)
myrs: Add Mylex RAID controller (SCSI interface)
drivers/block: Remove DAC960 driver
Documentation/blockdev/README.DAC960 | 756 ----
drivers/block/DAC960.c | 7244 ----------------------------------
drivers/block/DAC960.h | 4415 ---------------------
drivers/block/Kconfig | 12 -
drivers/block/Makefile | 1 -
drivers/scsi/Kconfig | 28 +
drivers/scsi/Makefile | 2 +
drivers/scsi/myrb.c | 3249 +++++++++++++++
drivers/scsi/myrb.h | 1891 +++++++++
drivers/scsi/myrs.c | 2947 ++++++++++++++
drivers/scsi/myrs.h | 2042 ++++++++++
drivers/scsi/raid_class.c | 1 +
include/linux/raid_class.h | 1 +
include/scsi/scsi_proto.h | 1 +
14 files changed, 10162 insertions(+), 12428 deletions(-)
delete mode 100644 Documentation/blockdev/README.DAC960
delete mode 100644 drivers/block/DAC960.c
delete mode 100644 drivers/block/DAC960.h
create mode 100644 drivers/scsi/myrb.c
create mode 100644 drivers/scsi/myrb.h
create mode 100644 drivers/scsi/myrs.c
create mode 100644 drivers/scsi/myrs.h
--
2.12.3
next reply other threads:[~2018-01-19 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 15:11 Hannes Reinecke [this message]
2018-01-19 15:11 ` [PATCH 1/5] raid_class: Add 'JBOD' RAID level Hannes Reinecke
2018-01-19 15:11 ` [PATCH 2/5] scsi: Add VENDOR_SPECIFIC sense code definitions Hannes Reinecke
2018-01-19 18:47 ` Bart Van Assche
2018-01-23 0:27 ` Martin K. Petersen
2018-01-19 15:11 ` [PATCH 3/5] myrb: Add Mylex RAID controller (block interface) Hannes Reinecke
2018-01-19 15:11 ` [PATCH 4/5] myrs: Add Mylex RAID controller (SCSI interface) 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=20180119151113.80768-1-hare@suse.de \
--to=hare@suse.de \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=jth@kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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;
as well as URLs for NNTP newsgroup(s).