From: "Adam Radford" <aradford@amcc.com>
To: hch@infradead.org, Jeff Garzik <jgarzik@pobox.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: RE: 2.6.6-mm5
Date: Sat, 22 May 2004 11:02:18 -0700 [thread overview]
Message-ID: <HY4NGC01.77W@hadar.amcc.com> (raw)
Hch,
I did try to CC linux-scsi in the original email for the 3ware driver submission/review,
and 2 emails since then. None of them went through (no bounce message either).
Does anybody know what the max email size is? Is it < 145k?
--
Adam Radford
Staff Software Engineer
AMCC
-----Original Message-----
From: linux-scsi-owner@vger.kernel.org
[mailto:linux-scsi-owner@vger.kernel.org]On Behalf Of hch@infradead.org
Sent: Saturday, May 22, 2004 2:23 AM
To: Jeff Garzik
Cc: Andrew Morton; linux-kernel@vger.kernel.org; SCSI Mailing List
Subject: Re: 2.6.6-mm5
On Sat, May 22, 2004 at 05:09:59AM -0400, Jeff Garzik wrote:
> Andrew Morton wrote:
> >- Added a new SATA RAID driver from 3ware. From a quick peek it seem to
> > need a little work yet.
>
>
> It's not too bad... but it looks more like a 2.2 driver forward ported
> to 2.4, than a 2.6.x driver. Needs some luvin' from the 2.6 scsi api crew.
>
> Overall, it appears to be a message-based firmware engine like
> drivers/block/carmel.c, that hides the SATA details in the firmware.
In addition driver submission should always go through linux-scsi. Please
tell them to submit it to linux-scsi so we can have a public review process
there.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2004-05-22 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-22 18:02 Adam Radford [this message]
[not found] <20040522013636.61efef73.akpm@osdl.org>
2004-05-22 9:09 ` 2.6.6-mm5 Jeff Garzik
2004-05-22 9:22 ` 2.6.6-mm5 hch
2004-05-22 9:26 ` 2.6.6-mm5 Andrew Morton
2004-05-22 11:51 ` 2.6.6-mm5 R. J. Wysocki
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=HY4NGC01.77W@hadar.amcc.com \
--to=aradford@amcc.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=jgarzik@pobox.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