public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Hannes Reinecke <hare@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Christoph Hellwig <hch@lst.de>,
	James Bottomley <james.bottomley@hansenpartnership.com>,
	Don Brace <don.brace@microsemi.com>, Meelis Roos <mroos@linux.ee>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCHv3 0/6] hpsa legacy support
Date: Wed, 16 Aug 2017 20:22:14 -0400	[thread overview]
Message-ID: <yq17ey3qc09.fsf@oracle.com> (raw)
In-Reply-To: <1502780289-127133-1-git-send-email-hare@suse.de> (Hannes Reinecke's message of "Tue, 15 Aug 2017 08:58:03 +0200")


Hannes,

> here's now the third attempt to add support for legacy boards, ie for
> boards previously supported by cciss only.  With this patchset the
> hpsa driver should work with all Smart Array boards if the
> 'hpsa_allow_any' module option is set, rendering the cciss driver
> obsolete.  Consequently I've added a patch to remove the cciss driver
> and make 'hpsa' an alias to 'cciss' and removed the 'hpsa_allow_any'
> module option.

Applied to 4.14/scsi-queue. Thank you!

-- 
Martin K. Petersen	Oracle Linux Engineering

      parent reply	other threads:[~2017-08-17  0:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15  6:58 [PATCHv3 0/6] hpsa legacy support Hannes Reinecke
2017-08-15  6:58 ` [PATCHv3 1/6] hpsa: add support for legacy boards Hannes Reinecke
2017-08-15  6:58 ` [PATCHv3 2/6] hpsa: disable volume status check " Hannes Reinecke
2017-08-15  6:58 ` [PATCHv3 3/6] hpsa: Ignore errors for unsupported LV_DEVICE_ID VPD page Hannes Reinecke
2017-08-15  6:58 ` [PATCHv3 4/6] hpsa: do not print errors for unsupported report luns format Hannes Reinecke
2017-08-15  6:58 ` [PATCHv3 5/6] cciss: Drop obsolete driver Hannes Reinecke
2017-08-15  6:58 ` [PATCHv3 6/6] hpsa: Remove 'hpsa_allow_any' module option Hannes Reinecke
2017-08-17  0:22 ` Martin K. Petersen [this message]

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=yq17ey3qc09.fsf@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=don.brace@microsemi.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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