From: Keith Owens <kaos@ocs.com.au>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] devexit fixes in i82092.c
Date: Sat, 16 Mar 2002 20:50:22 +1100 [thread overview]
Message-ID: <15665.1016272222@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sat, 16 Mar 2002 00:13:21 -0800." <Pine.LNX.4.33.0203160010510.2448-100000@home.transmeta.com>
On Sat, 16 Mar 2002 00:13:21 -0800 (PST),
Linus Torvalds <torvalds@transmeta.com> wrote:
>On Sat, 16 Mar 2002, Keith Owens wrote:
>>
>> Does that mean that we also get rid of the initcall methods? If
>> shutdown follows a device tree then startup should also use that tree.
>
>You cannot _build_ the tree without the initcall methods - it's populating
>the tree that the initcalls mostly do, after all.
Confusion of names. I read 'device tree' and thought you were talking
about an initialization tree that was built from PCI and USB data,
independent of kernel link order. If your 'device tree' is just the
existing initcall list derived from $(obj-y) then I agree that we
should bot have separate shutdown functions. module_exit should be
retained for objects that are built into the kernel and the shutdown
code should run the module_exit functions in reverse order to
initialization.
The question of separating register and probe is independent of the
above. It is definitely a good idea to separate register and probe, if
only to avoid all the existing races on module unload (using
__this_module and mod_inc_count everywhere in mainline code is not a
perfect solution).
next prev parent reply other threads:[~2002-03-16 9:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-16 0:57 Anders Gustafsson
2002-03-16 1:00 ` Linus Torvalds
2002-03-16 2:25 ` Jeff Garzik
2002-03-16 7:40 ` Linus Torvalds
2002-03-16 7:51 ` Keith Owens
2002-03-16 8:13 ` Linus Torvalds
2002-03-16 9:00 ` Jeff Garzik
2002-03-16 9:50 ` Keith Owens [this message]
2002-03-25 19:15 ` Patrick Mochel
2002-03-16 8:51 ` Jeff Garzik
2002-03-16 17:35 ` Alan Cox
2002-03-16 17:31 ` Jeff Garzik
2002-03-25 19:19 ` Patrick Mochel
2002-03-16 9:40 ` Arjan van de Ven
2002-03-22 15:47 ` Pavel Machek
2002-03-16 10:32 ` David Woodhouse
2002-03-16 19:27 ` Eric W. Biederman
2002-03-16 21:00 ` Alan Cox
2002-03-16 22:03 ` Eric W. Biederman
2002-03-16 22:28 ` Alan Cox
2002-03-16 22:16 ` Eric W. Biederman
2002-03-16 22:26 ` Linus Torvalds
2002-03-16 23:00 ` Eric W. Biederman
2002-03-16 23:15 ` Dave Jones
2002-03-21 15:12 ` Pavel Machek
2002-03-25 19:02 ` Patrick Mochel
2002-03-24 23:36 Alexander Stohr
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=15665.1016272222@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®