From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Miller <mike.miller@hp.com>
Cc: "Stephen M. Cameron" <scameron@beardog.cce.hp.com>,
James.Bottomley@HansenPartnership.com, axboe@kernel.dk,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
mikem@beardog.cce.hp.com, jowens@hp.com
Subject: Re: [PATCH] Add hpsa driver for HP Smart Array controllers.
Date: Sat, 3 Oct 2009 11:22:49 -0700 [thread overview]
Message-ID: <20091003112249.5fb1b241.akpm@linux-foundation.org> (raw)
In-Reply-To: <20091002191626.GA17862@beardog.cce.hp.com>
On Fri, 2 Oct 2009 14:16:26 -0500 Mike Miller <mike.miller@hp.com> wrote:
> On Thu, Oct 01, 2009 at 02:30:35PM -0700, Andrew Morton wrote:
> > On Thu, 01 Oct 2009 16:25:30 -0500
> > "Stephen M. Cameron" <scameron@beardog.cce.hp.com> wrote:
> >
> > > Add hpsa driver for HP Smart Array controllers.
> > >
> > > This driver supports a subset of HP Smart Array Controllers.
> > > It is a SCSI alternative to the cciss driver.
> >
> > Does it support all the devices which cciss supports?
> >
> > IOW, do we have a plan here to remove the cciss driver or must we
> > maintain both drivers indefinitely?
>
> Andrew, et al.,
> >From the lack of response I'm guessing my reply about phasing cciss out
> completely did not go over well. Or is that what the question meant?
>
> We purposely limited controller support in hpsa to try and prevent problems
> in the field. What's needed to get hpsa accepted? Add support for all
> hardware?
>
> While we do not want to maintain 2 drivers indefinitely we (HP) must
> continue to support cciss for some years to come.
>
> Any guidance is appreciated.
>
Well, obviously it's neater if we can retire the old driver. Sometimes
life isn't neat. We had a similar situation with e1000-vs-e1000e. And
with e100-vs-eepro100, although eepro100 went away after many years.
next prev parent reply other threads:[~2009-10-03 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 21:25 [PATCH] Add hpsa driver for HP Smart Array controllers Stephen M. Cameron
2009-10-01 21:30 ` Andrew Morton
2009-10-01 21:42 ` Mike Miller
2009-10-05 12:43 ` Hannes Reinecke
2009-10-02 19:16 ` Mike Miller
2009-10-03 18:22 ` Andrew Morton [this message]
2009-10-02 20:23 ` Rolf Eike Beer
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=20091003112249.5fb1b241.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=axboe@kernel.dk \
--cc=jowens@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mike.miller@hp.com \
--cc=mikem@beardog.cce.hp.com \
--cc=scameron@beardog.cce.hp.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