From: Dave Jones <davej@redhat.com>
To: Marc Zyngier <mzyngier@freesurf.fr>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org, akpm@osdl.org,
jgarzik@pobox.com
Subject: Re: [3C509] Fix sysfs leak.
Date: Tue, 16 Mar 2004 16:16:29 +0000 [thread overview]
Message-ID: <20040316161629.GD17958@redhat.com> (raw)
In-Reply-To: <wrpr7vseq06.fsf@panther.wild-wind.fr.eu.org>
On Tue, Mar 16, 2004 at 05:05:45PM +0100, Marc Zyngier wrote:
> #ifdef CONFIG_MCA
> mca_register_driver(&el3_mca_driver);
> #endif
> - return el3_cards ? 0 : -ENODEV;
> + return 0;
> }
>
> static void __exit el3_cleanup_module(void)
>
> This is not pretty either, but 3c579 probing will work, and in your
> case it won't leave a dangling directory in sysfs.
Yes, leaving the module around, and cleaning up at rmmod time should
also work. I'll test it in a while to be sure.
> Dave> Why is this even an issue so late on? Bus probing should have
> Dave> been done as part of bootup. By the time I get to modprobing
> Dave> device drivers, it should have been determined already.
>
> Modprobing is perfectly OK, and indeed everything has been probed at
> this stage.
Clearly it hadn't, or otherwise modprobing 3c509 would have failed
due to the lack of an eisa bus.
> But having built-in drivers raises a few different
> problems (the driver may be initialized before all busses are probed).
There were no built-in drivers in this case.
Dave
next prev parent reply other threads:[~2004-03-16 16:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 21:47 [3C509] Fix sysfs leak davej
2004-03-16 10:56 ` Marc Zyngier
2004-03-16 13:46 ` Dave Jones
2004-03-16 14:09 ` Marc Zyngier
2004-03-16 14:29 ` Dave Jones
2004-03-16 15:05 ` Marc Zyngier
2004-03-16 15:30 ` Dave Jones
2004-03-16 16:05 ` Marc Zyngier
2004-03-16 16:16 ` Dave Jones [this message]
2004-03-16 15:58 ` Richard B. Johnson
2004-03-19 16:36 ` Vojtech Pavlik
2004-03-16 16:06 ` Jeff Garzik
2004-03-16 16:13 ` Dave Jones
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=20040316161629.GD17958@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mzyngier@freesurf.fr \
--cc=torvalds@osdl.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