From: James Bottomley <James.Bottomley@steeleye.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "Smart, James" <James.Smart@Emulex.com>,
"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: [Announce] Emulex LightPulse Device Driver
Date: 10 Mar 2004 10:21:07 -0500 [thread overview]
Message-ID: <1078932070.1807.34.camel@mulgrave> (raw)
In-Reply-To: <404ED33D.3070504@pobox.com>
On Wed, 2004-03-10 at 03:35, Jeff Garzik wrote:
> Embark you shall, and let me join in the chorus of kudos for making the
> leap to open source. :)
Yes, I'll add my welcome to that.
[...]
> That should get you started ;-)
Actually, it would be my interpretation of the FAQ that most of this
work is already intended (although Jeff gave specific instances than the
generalities in the FAQ).
There were many more places than this in the driver that caused me to go
"good grief no". However, it probably makes more sense if you work down
your todo list and come back for a review when you're nearing the end of
it. That way you don't get boat loads of comments about things you were
planning to fix anyway.
James
next prev parent reply other threads:[~2004-03-10 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 22:45 [Announce] Emulex LightPulse Device Driver Smart, James
2004-03-10 0:09 ` Stefan Smietanowski
2004-03-10 7:21 ` vda
2004-03-10 8:35 ` Jeff Garzik
2004-03-10 15:21 ` James Bottomley [this message]
[not found] ` <mailman.1078908361.15239.linux-kernel2news@redhat.com>
2004-03-10 17:59 ` Pete Zaitcev
2004-03-10 18:04 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2004-03-10 22:47 Smart, James
2004-03-11 1:10 ` James Bottomley
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=1078932070.1807.34.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=James.Smart@Emulex.com \
--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