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] [day] [month] [year] [list]
Date:	Mon, 23 Sep 2013 11:09:40 +0000
From:	Amit Phansalkar <Amit.Phansalkar@...t.com>
To:	Jens Axboe <axboe@...nel.dk>, Olof Johansson <olof@...om.net>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Jeff Moyer <jmoyer@...hat.com>,
	OS Engineering <osengineering@...c-inc.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Akhil Bhansali <Akhil.Bhansali@...t.com>,
	Ramprasad Chinthekindi <Ramprasad.Chinthekindi@...t.com>
Subject: RE: [PATCH] block: Device driver for sTec's PCIe Kronos Card.

> -----Original Message-----
> From: Jens Axboe [mailto:axboe@...nel.dk]
> Sent: Monday, September 23, 2013 4:43 AM
> To: Olof Johansson
> Cc: Andrew Morton; Jeff Moyer; OS Engineering; linux-
> kernel@...r.kernel.org; Akhil Bhansali; Ramprasad Chinthekindi; Amit
> Phansalkar
> Subject: Re: [PATCH] block: Device driver for sTec's PCIe Kronos Card.
> 
> On Sun, Sep 22 2013, Olof Johansson wrote:
> > On Sat, Sep 21, 2013 at 1:01 PM, Jens Axboe <axboe@...nel.dk> wrote:
> > > On Fri, Sep 20 2013, Andrew Morton wrote:
> > >> On Tue, 17 Sep 2013 14:20:55 -0600 Jens Axboe <axboe@...nel.dk>
> wrote:
> > >>
> > >> > > So, it looks like this driver needs a bunch of work before it's
> > >> > > ready to go in. Or, maybe it's better to submit it with a TODO
> > >> > > list for the staging tree instead?
> > >> >
> > >> > Not disagreeing with you, it definitely needs a bit of cleaning.
> > >> > And so far stec has not been very responsive in fixing those issues.
> > >>
> > >> Geeze.  Here's what I came up with, mainly to make i386 compile:
> > >
> > > Thanks Andrew. It's not the fixes themselves that are tricky, I
> > > would just have liked a little more proof that the submission wasn't
> > > just a dump'n run.
> >
> > Well, that's what much of the staging process is about, since it needs
> > to come with a todo list (and that list needs to be taken care of
> > before the driver graduates). Honestly, this looks like a prime
> > candidate for that. But it's your tree and your call.
> >
> > Thanks for applying the patch from Andrew, that resolves most of it
> > for me right now.
> 
> I'm sort-of on the fence. It's minor stuff, but it does need cleaning up. So not
> necessarily something that will prevent it from going into 3.12, it's more the
> continued support and development I'm worried about.
> 

Hi Jens,

My name is Amit and I'm managing the host drivers team at sTec (now HGST). 

Thank you for your continued support and feedback in this effort. We are really committed to support this driver as part of Linux open source/kernel. I'd like to assure you that this is not a dump and run submission. In the recent past, we were working with Jeff to get this driver ready for open source and have been making necessary revisions. Even in future, my team would be available to investigate the issues and patch the driver accordingly. It would be great if you could consider this driver for 3.12 inclusion. 

Thanks and regards,
Amit Phansalkar


> --
> Jens Axboe


PROPRIETARY-CONFIDENTIAL INFORMATION INCLUDED

This electronic transmission, and any documents attached hereto, may contain confidential, proprietary and/or legally privileged information. The information is intended only for use by the recipient named above. If you received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of information received in error is strictly prohibited, and violators will be pursued legally.
--
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