From: Christoph Hellwig <hch@lst.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: James.Bottomley@hansenpartnership.com,
Christoph Hellwig <hch@lst.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Dave Jiang <dave.jiang@intel.com>,
David Milburn <dmilburn@redhat.com>,
Ed Ciechanowski <ed.ciechanowski@intel.com>,
Ed Nadolski <edmund.nadolski@intel.com>,
Jacek Danecki <jacek.danecki@intel.com>,
Jeff Skirvin <jeffrey.d.skirvin@intel.com>,
Jeff Garzik <jeff@garzik.org>
Subject: Re: [GIT PULL] isci merge candidate
Date: Sat, 14 May 2011 10:49:49 +0200 [thread overview]
Message-ID: <20110514084949.GA23984@lst.de> (raw)
In-Reply-To: <1305317680.21099.83.camel@dwillia2-linux>
On Fri, May 13, 2011 at 01:14:40PM -0700, Dan Williams wrote:
> The isci driver team has now completed the major rework items addressed
> in the review on linux-scsi (including removal of state handlers,
> merging lldd and 'core', cleaning up the source code layout).
I've looked over the driver a bit and I'm quite impressed with what
you're archived in the short time since taking over the driver from
whoever came up with the mess that it was initially.
I don't think you're quite done yet with the todo list that was given
to you yet. One thing that springs to mind is wrappers in timers.c,
which are not just ugly, but in case of isci_task_execute_tmf is plain
wrong as the implementation assumes all timers have the same lifetime
rules as the isci_host. You'll need to at least replace that last usage
with a direct wait_for_completion_timeout, and even better get rid
of it entirely.
Also not quite done yet, although I'm happy with postponing that for now
is the unification of the various data structures from the different
layers of the original driver, e.g. isci_phy vs scic_sds_phy,
isci_port vs scic_sds_port, isci_remote_device vs scic_sds_remote_device
and isci_request vs scic_sds_request.
And of course there's a lot of room for additional further cleanups
that should be able to shave off another couple thousands of lines, but
these never were on the plate for the initial merge anyway.
next prev parent reply other threads:[~2011-05-14 8:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 20:14 [GIT PULL] isci merge candidate Dan Williams
2011-05-13 20:34 ` Linus Torvalds
2011-05-13 21:45 ` Dan Williams
2011-05-13 22:16 ` Benjamin Herrenschmidt
2011-05-17 0:39 ` Dan Williams
2011-05-17 0:47 ` Jeff Garzik
2011-05-17 3:41 ` Douglas Gilbert
2011-05-13 21:46 ` Jeff Garzik
2011-05-14 8:49 ` Christoph Hellwig [this message]
2011-05-17 3:56 ` James Bottomley
2011-05-17 22:11 ` Dan Williams
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=20110514084949.GA23984@lst.de \
--to=hch@lst.de \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmilburn@redhat.com \
--cc=ed.ciechanowski@intel.com \
--cc=edmund.nadolski@intel.com \
--cc=jacek.danecki@intel.com \
--cc=jeff@garzik.org \
--cc=jeffrey.d.skirvin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).