All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Jens Axboe <axboe@kernel.dk>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Christoph Hellwig <hch@lst.de>,
	James Bottomley <james.bottomley@hansenpartnership.com>,
	linux-scsi@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCHv6 0/3] Deprecate DAC960 driver
Date: Wed, 17 Oct 2018 21:14:06 -0400	[thread overview]
Message-ID: <yq1lg6wkqe9.fsf@oracle.com> (raw)
In-Reply-To: <20181017152513.136526-1-hare@suse.de> (Hannes Reinecke's message of "Wed, 17 Oct 2018 17:25:10 +0200")


Hannes,

> 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'.

Applied to 4.20/scsi-queue since Jens already dropped the block driver.

Have you considered a dummy CONFIG_BLK_DEV_DAC960 config option like we
did when we merged mpt2sas and mpt3sas?

Also, does MODULE_ALIAS do the right thing when a driver is split into
two distinct modules?

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2018-10-18  1:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-17 15:25 [PATCHv6 0/3] Deprecate DAC960 driver Hannes Reinecke
2018-10-17 15:25 ` [PATCH 1/3] myrb: Add Mylex RAID controller (block interface) Hannes Reinecke
2018-10-17 15:25 ` [PATCH 2/3] myrs: Add Mylex RAID controller (SCSI interface) Hannes Reinecke
2018-10-17 15:25 ` [PATCH 3/3] drivers/block: Remove DAC960 driver Hannes Reinecke
2018-10-17 15:43 ` [PATCHv6 0/3] Deprecate " Jens Axboe
2018-10-18  1:14 ` Martin K. Petersen [this message]
2018-10-18  5:54   ` Hannes Reinecke
2018-10-19 22:26     ` Martin K. Petersen

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=yq1lg6wkqe9.fsf@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=axboe@kernel.dk \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=linux-block@vger.kernel.org \
    --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.