From: Christoph Hellwig <hch@infradead.org>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-block@vger.kernel.org, Don Brace <don.brace@microsemi.com>,
Scott Benesh <scott.benesh@microsemi.com>,
Scott Teel <scott.teel@microsemi.com>,
Kevin Barnett <kevin.barnett@microsemi.com>,
linux-scsi@vger.kernel.org
Subject: device support in hpasa, was: Re: OOPS from cciss_ioctl in 4.12+git
Date: Fri, 7 Jul 2017 08:00:42 -0700 [thread overview]
Message-ID: <20170707150042.GA15445@infradead.org> (raw)
In-Reply-To: <alpine.LRH.2.20.1707061236010.6514@math.ut.ee>
On Thu, Jul 06, 2017 at 12:55:04PM +0300, Meelis Roos wrote:
> > Also we're trying to move people away from the cciss driver, can you
> > check if the hpsa SCSI driver works for you as well?
>
> I have older adapter:
>
> Compaq Computer Corporation Smart Array 64xx [0e11:0046] (rev 01)
>
> That does not seem to be supported by hpsa AFAICS.
Looks like. Although hpsa has support for various SA5 controllers
it seems like it decided to skip all Compaq branded controllers.
As far as I can tell we could simply add support for those to
hpsa. Ccing hpsa folks to figure out if that's the case.
next prev parent reply other threads:[~2017-07-07 15:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 12:58 OOPS from cciss_ioctl in 4.12+git Meelis Roos
2017-07-05 22:51 ` Christoph Hellwig
2017-07-06 9:55 ` Meelis Roos
2017-07-07 15:00 ` Christoph Hellwig [this message]
2017-07-07 15:03 ` device support in hpasa, was: " Jens Axboe
2017-07-07 15:42 ` Laurence Oberman
2017-07-07 18:08 ` device support in hpsa, " Christoph Hellwig
2017-07-07 18:20 ` Laurence Oberman
2017-07-10 14:08 ` Meelis Roos
2017-07-10 21:56 ` Don Brace
2017-07-07 16:05 ` device support in hpasa, " Hannes Reinecke
2017-07-07 19:15 ` Don Brace
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=20170707150042.GA15445@infradead.org \
--to=hch@infradead.org \
--cc=don.brace@microsemi.com \
--cc=kevin.barnett@microsemi.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=scott.benesh@microsemi.com \
--cc=scott.teel@microsemi.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).