From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Don Brace <don.brace@microsemi.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
"jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
Viswas G <viswas.g@microsemi.com>,
Mahesh Rajashekhara <mahesh.rajashekhara@microsemi.com>,
"hch@infradead.org" <hch@infradead.org>,
Scott Teel <scott.teel@microsemi.com>,
Kevin Barnett <kevin.barnett@microsemi.com>,
Justin Lindley <justin.lindley@microsemi.com>,
Scott Benesh <scott.benesh@microsemi.com>,
"elliott@hpe.com" <elliott@hpe.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH V4 0/2] smartpqi: initial commit of Microsemi smartpqi driver
Date: Mon, 08 Aug 2016 21:04:42 -0400 [thread overview]
Message-ID: <yq1tweuvjkl.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <4993A297653ECB4581FA5C3C31323D19163937F2@avsrvexchmbx1.microsemi.net> (Don Brace's message of "Fri, 5 Aug 2016 14:19:20 +0000")
>>>>> "Don" == Don Brace <don.brace@microsemi.com> writes:
>> Is your interface related to T10 PQI?
Don> We follow it pretty closely with some exceptions: - Our memory BARS
Don> includes both the aacraid SIS and PQI interfaces - We have our own
Don> config table defined. - We are using our own error data buffer
Don> schema - We are not yet supporting fencing and some other features.
OK. I was just wondering whether it would make sense to have a libpqi
with all the spec-compliant pieces and put the "smart" in a dedicated
Microsemi driver.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2016-08-09 1:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 21:40 [PATCH V4 0/2] smartpqi: initial commit of Microsemi smartpqi driver Don Brace
2016-06-27 21:41 ` [PATCH V4 1/2] " Don Brace
2016-08-01 7:13 ` Hannes Reinecke
2016-08-01 8:17 ` Johannes Thumshirn
2016-08-10 16:12 ` Ewan D. Milne
2016-06-27 21:41 ` [PATCH V4 2/2] aacraid: remove wildcard for series 9 controllers Don Brace
2016-08-10 16:14 ` Ewan D. Milne
2016-08-12 20:08 ` Martin K. Petersen
2016-09-07 21:04 ` Don Brace
2016-09-08 18:15 ` Don Brace
2016-09-08 18:25 ` James Bottomley
2016-09-08 18:33 ` Scott Benesh
2016-09-08 22:38 ` James Bottomley
2016-09-09 16:06 ` Scott Benesh
2016-10-03 20:09 ` Don Brace
2016-11-11 14:47 ` Don Brace
2016-12-07 21:44 ` Don Brace
2016-12-08 0:10 ` Martin K. Petersen
2016-10-14 15:41 ` Don Brace
2016-09-09 17:11 ` David Carroll
2016-08-05 1:24 ` [PATCH V4 0/2] smartpqi: initial commit of Microsemi smartpqi driver Martin K. Petersen
2016-08-05 14:19 ` Don Brace
2016-08-09 1:04 ` Martin K. Petersen [this message]
2016-08-09 15:37 ` Don Brace
2016-08-11 2:25 ` Martin K. Petersen
2016-08-11 21:13 ` Don Brace
2016-08-12 20:10 ` Martin K. Petersen
2016-08-15 15:54 ` Don Brace
2016-08-17 2:28 ` 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=yq1tweuvjkl.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=don.brace@microsemi.com \
--cc=elliott@hpe.com \
--cc=hch@infradead.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=justin.lindley@microsemi.com \
--cc=kevin.barnett@microsemi.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mahesh.rajashekhara@microsemi.com \
--cc=scott.benesh@microsemi.com \
--cc=scott.teel@microsemi.com \
--cc=viswas.g@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 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.