From: Christoph Hellwig <hch@infradead.org>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] dpt_i2o pci_driver model
Date: Fri, 19 Aug 2005 15:59:02 +0100 [thread overview]
Message-ID: <20050819145902.GA2015@infradead.org> (raw)
In-Reply-To: <547AF3BD0F3F0B4CBDC379BAC7E4189F01709253@otce2k03.adaptec.com>
On Wed, Aug 17, 2005 at 01:04:05PM -0400, Salyzyn, Mark wrote:
> Christoph Hellwig [mailto:hch@infradead.org] writes:
> > ... update the driver to use the pci_driver model ...
>
> The patch applies to the scsi-misc-2.6 git tree. The moving of
> adpt_install_hba to the near bottom of the dpt_i2o.c file creates a
> dirty context diff in that region which is hard to inspect from within
> the patch. No coding style changes were made when moving content from
> the original initialization code to the module_init and module_exit
> functions to aid before and after comparisons for inspection; even
> despite the fact C++ style comments are used in these sections. We
> expect such style cleanup to occur either on any necessary follow-up
> rewrites after basic functional approval, or as a follow-up cleanup
> patch.
This looks wrong to me. It's still walking a lot of driver-global
hba lists in the init routine. All hba initialization should happen
in the ->probe callback, and there should be very little global
initialization. There shouldn't really be any global list of hbas.
next prev parent reply other threads:[~2005-08-19 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 17:04 [PATCH] dpt_i2o pci_driver model Salyzyn, Mark
2005-08-19 14:59 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-19 15:05 Salyzyn, Mark
2005-09-06 11:45 ` Christoph Hellwig
2005-09-06 12:28 Salyzyn, Mark
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=20050819145902.GA2015@infradead.org \
--to=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.