From: Jeff Garzik <jeff@garzik.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Broadcom 8603 SAS/SATA driver, rough draft
Date: Mon, 24 Sep 2007 11:30:36 -0400 [thread overview]
Message-ID: <46F7D81C.8030804@garzik.org> (raw)
In-Reply-To: <1190642806.3355.12.camel@localhost.localdomain>
James Bottomley wrote:
> On the other hand, I think I can find a nice lever to move Marvell with,
> so I'll take this on without needing potentially to compromise your
> contacts.
FWIW Marvell is moving quite nicely... they are actively providing docs
under NDA, and sometimes sample code (or even a GPL driver) to active
developers. Still trying to push them on opening docs, but one step at
a time :)
Jeff
prev parent reply other threads:[~2007-09-24 15:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-23 4:04 [PATCH] Broadcom 8603 SAS/SATA driver, rough draft Jeff Garzik
2007-09-23 21:59 ` Douglas Gilbert
2007-09-23 23:33 ` Jeff Garzik
2007-09-23 23:46 ` Jeff Garzik
2007-09-23 23:47 ` Jeff Garzik
2007-09-23 23:05 ` James Bottomley
2007-09-23 23:43 ` Jeff Garzik
2007-09-23 23:59 ` James Bottomley
2007-09-24 0:14 ` Jeff Garzik
2007-09-24 14:06 ` James Bottomley
2007-09-24 15:30 ` Jeff Garzik [this message]
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=46F7D81C.8030804@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-kernel@vger.kernel.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