From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Hannes Reinecke <hare@suse.de>,
Christoph Hellwig <hch@infradead.org>,
"Reddy, Sreekanth" <Sreekanth.Reddy@avagotech.com>,
Sathya.Prakash@avagotech.com,
Nagalakshmi.Nandigama@avagotech.com, linux-scsi@vger.kernel.org
Subject: Re: mpt2sas and mpt3sas merge (again)
Date: Mon, 14 Jul 2014 17:34:06 -0400 [thread overview]
Message-ID: <yq1bnsry69d.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <1405347425.2395.5.camel@dabdike.int.hansenpartnership.com> (James Bottomley's message of "Mon, 14 Jul 2014 07:17:05 -0700")
>>>>> "James" == James Bottomley <James.Bottomley@HansenPartnership.com> writes:
James> I support the concept, since I think everyone told LSI at the
James> time that splitting the drivers would become a maintenance
James> nightmare.
And it is. I'd like to see these drivers merged as well.
James> One of the big reasons we don't have a lot of leverage with them
James> is that they always seem to slide updates around upstream via the
James> distros (often, it has to be admitted the DKM route), so if Red
James> Hat, SUSE, Oracle and Canonical can agree not to accept LSI
James> updates until the driver is done this way, we'd have a lot more
James> leverage.
Unless it's a trivial bug fix Oracle won't take anything that's not
accepted upstream. We are working with Avago/LSI to streamline their
driver process to be a better fit for both upstream development and
distro kernels.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2014-07-14 21:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 8:35 mpt2sas and mpt3sas merge (again) Christoph Hellwig
2014-07-14 9:22 ` Hannes Reinecke
2014-07-14 14:17 ` James Bottomley
2014-07-14 14:39 ` Hannes Reinecke
2014-07-14 14:57 ` James Bottomley
2014-07-14 15:10 ` Hannes Reinecke
2014-07-14 17:00 ` Tomas Henzl
2014-07-14 21:34 ` Martin K. Petersen [this message]
[not found] ` <CAK=zhgoD9vVH0zCORTA2Mhu8Tf4m4VAih_hpig4PDdh-vgJmQg@mail.gmail.com>
2014-07-23 1:39 ` Martin K. Petersen
2014-07-24 12:25 ` Sreekanth Reddy
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=yq1bnsry69d.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Nagalakshmi.Nandigama@avagotech.com \
--cc=Sathya.Prakash@avagotech.com \
--cc=Sreekanth.Reddy@avagotech.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
/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