From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "Saxena, Sumit" <Sumit.Saxena@lsi.com>
Cc: Ben Collins <ben.c@servergy.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
DL-MegaRAID Linux <megaraidlinux@lsi.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
"aradford@gmail.com" <aradford@gmail.com>,
"Maloy, Joe" <Joe.Maloy@lsi.com>
Subject: Re: State of big-endian for MegaRAID SAS driver
Date: Mon, 26 Aug 2013 19:25:25 -0400 [thread overview]
Message-ID: <yq17gf83uhm.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <088E451FE1854947BD9145EF8C016FF413A017BC30@inbmail01.lsi.com> (Sumit Saxena's message of "Mon, 26 Aug 2013 12:51:07 +0530")
>>>>> "Sumit" == Saxena, Sumit <Sumit.Saxena@lsi.com> writes:
>> I realize that the big-endian patch from Martin isn't complete for
>> fusion, but it is for other cards.
Correct. I had no interest in Fury/Invader and no access to those
boards.
Sumit> Martin's patch does not have few changes needed in function
Sumit> "megasas_init_fw()"(inside file: megaraid_sas_base.c),
Patches welcome!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2013-08-26 23:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 16:57 State of big-endian for MegaRAID SAS driver Ben Collins
2013-08-14 18:11 ` Martin K. Petersen
2013-08-14 19:32 ` Martin K. Petersen
[not found] ` <D354E621-BEFA-4010-B5CF-4668939AAEB0@servergy.com>
2013-08-14 19:44 ` Martin K. Petersen
2013-08-15 2:52 ` Ben Collins
2013-08-16 1:12 ` Martin K. Petersen
2013-08-19 11:16 ` Saxena, Sumit
2013-08-19 17:25 ` Ben Collins
2013-08-26 7:21 ` Saxena, Sumit
2013-08-26 9:05 ` Christoph Hellwig
2013-08-26 20:15 ` Maloy, Joe
2013-08-26 20:26 ` Ben Collins
2013-08-26 20:43 ` Christoph Hellwig
2013-08-26 20:41 ` Christoph Hellwig
2013-08-26 22:35 ` Maloy, Joe
2013-08-26 23:22 ` Ben Collins
2013-08-26 23:25 ` Martin K. Petersen [this message]
2013-08-26 23:45 ` 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=yq17gf83uhm.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=Joe.Maloy@lsi.com \
--cc=Sumit.Saxena@lsi.com \
--cc=aradford@gmail.com \
--cc=ben.c@servergy.com \
--cc=linux-scsi@vger.kernel.org \
--cc=megaraidlinux@lsi.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