From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Moore, Eric Dean" <Eric.Moore@lsil.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: RE: [patch 6/8] mptfusion: fc transport
Date: 06 Dec 2004 11:20:47 -0600 [thread overview]
Message-ID: <1102353654.1714.17.camel@mulgrave> (raw)
In-Reply-To: <91888D455306F94EBD4D168954A9457C734893@nacos172.co.lsil.com>
On Mon, 2004-12-06 at 11:12, Moore, Eric Dean wrote:
> Our concern is the impact to linux distributions installers and
> end users that upgrade to these newer drivers.
> Example: Someone having older driver using boot device attached
> to our controller. Then they download a newer kernel from Kernel.org with
> newer
> drivers having mptfc. They mkinitrd, or mk_initrd (without modifing
> linuxrc),
> reboot then what? Can they see the boot partition?
That's a concern only for people who boot from your fibre adapters. How
many such users are there?
> Can we change the time when LLDs register themselves to the
> transport layer? Like from the probe routine.
Well, not really, unless you have a proposal to get around the
fundamental problem Christoph already pointed out: any reference to the
fc_ transport methods will automatically cause modprobe to load it
regardless of whether it is used.
James
next prev parent reply other threads:[~2004-12-06 17:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 17:12 [patch 6/8] mptfusion: fc transport Moore, Eric Dean
2004-12-06 17:20 ` James Bottomley [this message]
-- 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-03 17:33 Moore, Eric Dean
2004-12-03 18:17 ` Christoph Hellwig
2004-12-06 15:18 ` 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=1102353654.1714.17.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Eric.Moore@lsil.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