From: Christoph Hellwig <hch@infradead.org>
To: "Smart, James" <James.Smart@Emulex.Com>
Cc: Linux SCSI Reflector <linux-scsi@vger.kernel.org>
Subject: Re: [Emulex] Ready for next round...
Date: Wed, 16 Jun 2004 09:17:57 +0100 [thread overview]
Message-ID: <20040616081757.GA8683@infradead.org> (raw)
In-Reply-To: <3356669BBE90C448AD4645C843E2BF28034F94D5@xbl.ma.emulex.com>
On Tue, Jun 15, 2004 at 01:32:56PM -0400, Smart, James wrote:
> Christoph, et al...
>
> I'd like to request the next round of review comments on the driver.
>
> We believe that tonights posting on SourceForge has addressed all of the
> comments to date with only a couple of exceptions (see below).
Before commenting on anything here's a big diff turning lpfc_fcp.c into
normal driver function ordering, aka function above invokations, scsi
methods over pci methods, and fixes gazillions of leaks in the ->probe
failure cases. It's guranteed to conflict with just about everything
touching that file.
next prev parent reply other threads:[~2004-06-16 8:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 17:32 [Emulex] Ready for next round Smart, James
2004-06-16 8:17 ` Christoph Hellwig [this message]
2004-06-16 13:35 ` Jamie Wellnitz
2004-06-16 13:50 ` Christoph Hellwig
2004-06-16 8:20 ` Christoph Hellwig
2004-06-16 8:31 ` Christoph Hellwig
2004-06-20 13:35 ` Christoph Hellwig
2004-06-23 15:31 ` Anton Blanchard
-- strict thread matches above, loose matches on Subject: below --
2004-06-18 19:56 Smart, James
2004-06-18 20:58 ` 'Christoph Hellwig'
2004-07-09 19:24 Smart, James
2004-07-09 22:08 ` 'Christoph Hellwig'
2004-07-09 22:10 ` 'Christoph Hellwig'
2004-07-17 11:26 Smart, James
2004-07-17 20:17 ` 'Christoph Hellwig'
2004-07-17 20:26 ` 'Christoph Hellwig'
2004-07-19 20:02 Ely, Paul
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=20040616081757.GA8683@infradead.org \
--to=hch@infradead.org \
--cc=James.Smart@Emulex.Com \
--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