linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	linux-scsi@vger.kernel.org, linux-block@vger.kernel.org,
	Hannes Reinecke <hare@suse.de>
Subject: [PATCH 0/4]  mylex: Replace DAC960 block driver
Date: Wed,  2 Aug 2017 16:13:24 +0200	[thread overview]
Message-ID: <1501683208-5240-1-git-send-email-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.
The new driver is called 'mylex'.

The Mylex/DAC960 HBA comes in two flavours; the later one (V2) already
has a pretty complete SCSI emulation layer, so we just have to reformat
the command.
For for earlier ones (V1) we don't have a SCSI emulation layer for the
logical drives, so I've added a (pretty rudimentary, admittedly) SCSI
translation for them.
And the weird proc interface has been converted to sysfs attributes.

Tested with eXtremeRAID 1100 (for V1 Firmware) and Mylex AcceleRAID 170
(for V2 Firmware).

As usual, comments and reviews are welcome.

Hannes Reinecke (4):
  raid_class: Add 'JBOD' RAID level
  scsi: Add VENDOR_SPECIFIC sense code definitions
  scsi: add Mylex RAID controller
  block: Drop obsolete DAC960 driver

 Documentation/blockdev/README.DAC960 |  756 ----
 drivers/block/DAC960.c               | 7241 ----------------------------------
 drivers/block/DAC960.h               | 4415 ---------------------
 drivers/block/Kconfig                |   12 -
 drivers/block/Makefile               |    1 -
 drivers/scsi/Kconfig                 |   12 +
 drivers/scsi/Makefile                |    1 +
 drivers/scsi/mylex.c                 | 6025 ++++++++++++++++++++++++++++
 drivers/scsi/mylex.h                 | 4029 +++++++++++++++++++
 drivers/scsi/raid_class.c            |    1 +
 include/linux/raid_class.h           |    1 +
 include/scsi/scsi_proto.h            |    1 +
 12 files changed, 10070 insertions(+), 12425 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/mylex.c
 create mode 100644 drivers/scsi/mylex.h

-- 
1.8.5.6

             reply	other threads:[~2017-08-02 14:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 14:13 Hannes Reinecke [this message]
2017-08-02 14:13 ` [PATCH 1/4] raid_class: Add 'JBOD' RAID level Hannes Reinecke
2017-08-02 14:13 ` [PATCH 2/4] scsi: Add VENDOR_SPECIFIC sense code definitions Hannes Reinecke
2017-08-02 14:13 ` [PATCH 3/4] scsi: add Mylex RAID controller Hannes Reinecke
2017-08-05 11:39   ` Christoph Hellwig
2017-08-07  6:09     ` Hannes Reinecke
2017-08-09 14:10       ` Christoph Hellwig
2017-08-09 15:11         ` Hannes Reinecke
2017-08-02 14:13 ` [PATCH 4/4] block: Drop obsolete DAC960 driver Hannes Reinecke
2017-08-09 14:23 ` [PATCH 0/4] mylex: Replace DAC960 block driver Christoph Hellwig
2017-08-09 15:09   ` Hannes Reinecke
2018-01-08 11:25 ` Christoph Hellwig

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=1501683208-5240-1-git-send-email-hare@suse.de \
    --to=hare@suse.de \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=jth@kernel.org \
    --cc=linux-block@vger.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).