lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 3 Oct 2009 11:22:49 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Mike Miller <mike.miller@...com>
Cc:	"Stephen M. Cameron" <scameron@...rdog.cce.hp.com>,
	James.Bottomley@...senPartnership.com, axboe@...nel.dk,
	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
	mikem@...rdog.cce.hp.com, jowens@...com
Subject: Re: [PATCH] Add hpsa driver for HP Smart Array controllers.

On Fri, 2 Oct 2009 14:16:26 -0500 Mike Miller <mike.miller@...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@...rdog.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.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ