From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Moore, Eric Dean" <Eric.Moore@lsil.com>
Cc: Magnus Damm <damm@opensource.se>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
mpt_linux_developer@lsil.com
Subject: RE: [PATCH] mptscsih: MODULE_PARM() -> module_param()
Date: Tue, 12 Apr 2005 11:38:19 -0500 [thread overview]
Message-ID: <1113323900.5774.35.camel@mulgrave> (raw)
In-Reply-To: <91888D455306F94EBD4D168954A9457C01DBBC2C@nacos172.co.lsil.com>
On Tue, 2005-04-05 at 14:30 -0600, Moore, Eric Dean wrote:
> Ok fine - This fix is already there in the series of patches
> I provided a week ago for splitting the mpt fusion drivers
> into seperate bus type drivers.
>
> James any word on whether those series of patches will get
> approved?
The patches themselves look fine. However, there's a problem which I
just discovered on putting it together and taking it for a test spin:
the MODULE_DEVICE_TABLE directive is still in mptbase. This means that
the udev/hotplug system thinks that when it's loaded mptbase
everything's done, which now means that everyone loses their devices
since the upper drivers aren't loaded. To make this all work and keep
the distros happy, the MODULE_DEVICE_TABLE has to be split out and
placed into the mptspi or mptfc components.
James
next prev parent reply other threads:[~2005-04-12 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 20:30 [PATCH] mptscsih: MODULE_PARM() -> module_param() Moore, Eric Dean
2005-04-05 22:10 ` Magnus Damm
2005-04-12 16:38 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-13 16:02 Moore, Eric Dean
2005-04-05 19:18 Magnus Damm
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=1113323900.5774.35.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Eric.Moore@lsil.com \
--cc=damm@opensource.se \
--cc=linux-scsi@vger.kernel.org \
--cc=mpt_linux_developer@lsil.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox