From: Christoph Hellwig <hch@infradead.org>
To: Ben Collins <bcollins@ubuntu.com>
Cc: "Maloy, Joe" <Joe.Maloy@lsi.com>,
Christoph Hellwig <hch@infradead.org>,
"Saxena, Sumit" <Sumit.Saxena@lsi.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>,
"Maly, JoLyn" <JoLyn.Maly@lsi.com>
Subject: Re: State of big-endian for MegaRAID SAS driver
Date: Mon, 26 Aug 2013 13:43:19 -0700 [thread overview]
Message-ID: <20130826204319.GB26624@infradead.org> (raw)
In-Reply-To: <AA2AC8A7-DD06-4AC5-9E4D-E522F6AC1B09@ubuntu.com>
On Mon, Aug 26, 2013 at 04:26:30PM -0400, Ben Collins wrote:
> Historically, waiting on commercial upstream to deliver what the community has already done is wasted time. Likewise, historically, allowing patches that partially implement things (in this respect, support one generation of card for megaraid_sas) leads to further support from the community, in a much faster timefram
*nod* Also historically ignoring hardware vendor mangement chains has
always lead to better drivers. Not saying that some vendors don't have
competent engineer (many do, mand don't), but as soon as management gets
involved in decisions about drivers all hope is lost.
next prev parent reply other threads:[~2013-08-26 20:43 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 [this message]
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
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=20130826204319.GB26624@infradead.org \
--to=hch@infradead.org \
--cc=JoLyn.Maly@lsi.com \
--cc=Joe.Maloy@lsi.com \
--cc=Sumit.Saxena@lsi.com \
--cc=aradford@gmail.com \
--cc=bcollins@ubuntu.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--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