From: Christoph Hellwig <hch@infradead.org>
To: "Moore, Eric Dean" <Eric.Moore@lsil.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [patch 6/8] mptfusion: fc transport
Date: Fri, 3 Dec 2004 18:17:36 +0000 [thread overview]
Message-ID: <20041203181736.GA15916@infradead.org> (raw)
In-Reply-To: <91888D455306F94EBD4D168954A9457C73423E@nacos172.co.lsil.com>
On Fri, Dec 03, 2004 at 10:33:17AM -0700, Moore, Eric Dean wrote:
> Why does spi_attach_transport or fc_attach_transport have to be
> done from the module_init routines? Meaning there is an assumption
> that spi and FC are separate drivers. Why can't the xxx_attach_transport be
> done
> later from the probe routines when we know which pci devices we are
> attaching?
That's fine. But as soon as a module uses symbols from another module that
second module needs to be loaded.
But I think splitting doesn't make a lot of sense here, we can introduce
config options to disable SPI/FC/SAS support so people building custom
kernels don't waste memory.
next prev parent reply other threads:[~2004-12-03 18:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 17:33 [patch 6/8] mptfusion: fc transport Moore, Eric Dean
2004-12-03 18:17 ` Christoph Hellwig [this message]
2004-12-06 15:18 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2005-01-13 19:14 Moore, Eric Dean
2004-12-07 0:29 Moore, Eric Dean
2005-01-08 21:33 ` James Bottomley
2004-12-06 17:12 Moore, Eric Dean
2004-12-06 17:20 ` James Bottomley
2004-12-01 23:40 Moore, Eric Dean
2004-12-01 19:46 Moore, Eric Dean
2004-12-01 20:49 ` James Bottomley
2004-11-19 15:39 Moore, Eric Dean
2004-11-25 20:54 ` James Bottomley
2004-11-18 23:33 Moore, Eric Dean
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=20041203181736.GA15916@infradead.org \
--to=hch@infradead.org \
--cc=Eric.Moore@lsil.com \
--cc=James.Bottomley@SteelEye.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 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.