From: Hannes Reinecke <hare@suse.de>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
James Bottomley <james.bottomley@hansenpartnership.com>,
Kashyap Desai <kashyap.desai@broadcom.com>,
Sumit Saxena <sumit.saxena@broadcom.com>,
linux-scsi@vger.kernel.org, Hannes Reinecke <hare@suse.de>
Subject: [PATCH 0/2] Drop legacy megaraid implementation
Date: Fri, 30 Jun 2017 13:05:52 +0200 [thread overview]
Message-ID: <1498820754-51032-1-git-send-email-hare@suse.de> (raw)
The legacy megaraid implementation is ancient, and support for most boards
has been moved to megaraid_mm anyway. So drop the legacy implementation.
And do not refer to 'megaraid_mm' as a 'new driver'; it's close to be obsoleted
itself.
Hannes Reinecke (2):
Drop legacy megaraid controller
megaraid: drop the 'new driver' statements
MAINTAINERS | 1 -
drivers/scsi/Makefile | 1 -
drivers/scsi/megaraid.c | 4730 --------------------------------
drivers/scsi/megaraid.h | 1010 -------
drivers/scsi/megaraid/Kconfig.megaraid | 17 +-
5 files changed, 3 insertions(+), 5756 deletions(-)
delete mode 100644 drivers/scsi/megaraid.c
delete mode 100644 drivers/scsi/megaraid.h
--
1.8.5.6
next reply other threads:[~2017-06-30 11:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 11:05 Hannes Reinecke [this message]
2017-06-30 11:05 ` [PATCH 1/2] Drop legacy megaraid controller Hannes Reinecke
2017-06-30 17:33 ` Christoph Hellwig
2017-06-30 18:15 ` Hannes Reinecke
2017-07-03 7:50 ` Sumit Saxena
2017-07-04 15:09 ` Hannes Reinecke
2017-06-30 11:05 ` [PATCH 2/2] megaraid: drop the 'new driver' statements 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=1498820754-51032-1-git-send-email-hare@suse.de \
--to=hare@suse.de \
--cc=hch@lst.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=kashyap.desai@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sumit.saxena@broadcom.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 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.