From: Jeremy Higdon <jeremy@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH 1/1] sgiioc4: Disable module unload
Date: Tue, 21 Nov 2006 17:59:52 -0800 [thread overview]
Message-ID: <20061122015952.GH75625@sgi.com> (raw)
In-Reply-To: <20061121172816.63495f1f.akpm@osdl.org>
On Tue, Nov 21, 2006 at 05:28:16PM -0800, Andrew Morton wrote:
> On Mon, 20 Nov 2006 19:15:52 -0800
> Jeremy Higdon <jeremy@sgi.com> wrote:
>
> > This patch removes a module_exit function that it sgiioc4 should not have had.
> >
> > Signed-off-by: Jeremy Higdon <jeremy@sgi.com>
> >
> >
> > --- linux-2.6.19-rc6/drivers/ide/pci/sgiioc4.c 2006-11-15 20:03:40.000000000 -0800
> > +++ linux-2.6.19-rc6-mod/drivers/ide/pci/sgiioc4.c 2006-11-20 18:45:08.506724280 -0800
> > @@ -768,14 +768,7 @@
> > return ioc4_register_submodule(&ioc4_ide_submodule);
> > }
> >
> > -static void __devexit
> > -ioc4_ide_exit(void)
> > -{
> > - ioc4_unregister_submodule(&ioc4_ide_submodule);
> > -}
> > -
> > late_initcall(ioc4_ide_init); /* Call only after IDE init is done */
> > -module_exit(ioc4_ide_exit);
> >
> > MODULE_AUTHOR("Aniket Malatpure/Jeremy Higdon");
> > MODULE_DESCRIPTION("IDE PCI driver module for SGI IOC4 Base-IO Card");
>
> Why? We'd prefer that the module be unloadable, wouldn't we?
It seems that the IDE layer doesn't support that. sgiioc4 was the only
driver in drivers/ide/pci that had an exit function. After an unload,
the devices would stay around and the next attempt to reference would
crash...
Thanks,
jeremy
next prev parent reply other threads:[~2006-11-22 1:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 3:15 [PATCH 1/1] sgiioc4: Disable module unload Jeremy Higdon
2006-11-22 1:28 ` Andrew Morton
2006-11-22 1:59 ` Jeremy Higdon [this message]
2006-11-22 2:13 ` Andrew Morton
2006-11-22 20:29 ` Bartlomiej Zolnierkiewicz
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=20061122015952.GH75625@sgi.com \
--to=jeremy@sgi.com \
--cc=akpm@osdl.org \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).