From: "David S. Miller" <davem@redhat.com>
To: mochel@osdl.org
Cc: anton@samba.org, linux-kernel@vger.kernel.org
Subject: Re: [2.5.19] Oops during PCI scan on Alpha
Date: Tue, 04 Jun 2002 11:13:37 -0700 (PDT) [thread overview]
Message-ID: <20020604.111337.51699424.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0206040821100.654-100000@geena.pdx.osdl.net>
From: Patrick Mochel <mochel@osdl.org>
Date: Tue, 4 Jun 2002 08:50:11 -0700 (PDT)
On Sun, 2 Jun 2002, David S. Miller wrote:
> It's happening on every platform. It should be done before
> arch_initcalls actually, but after core_initcalls. I would suggest to
> rename unused_initcall into postcore_iniscall, then use it for this
> and sys_bus_init which has the same problem.
Can't it go the other way? Instead of mass-promotion of the setup
functions, can't we demote the ones that are causing the problems?
There's this middle area between core and subsys, why not
just be explicit about it's existence?
Short of making the true dependencies describable, I think my
postcore_initcall solution is fine.
next prev parent reply other threads:[~2002-06-04 18:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 20:06 [2.5.19] Oops during PCI scan on Alpha Jan-Benedict Glaw
2002-06-03 4:27 ` Anton Blanchard
2002-06-03 3:39 ` David S. Miller
2002-06-04 15:50 ` Patrick Mochel
2002-06-04 17:07 ` Ivan Kokshaysky
2002-06-04 18:58 ` Patrick Mochel
2002-06-04 18:26 ` Benjamin Herrenschmidt
2002-06-05 14:20 ` Ivan Kokshaysky
2002-06-04 18:13 ` David S. Miller [this message]
2002-06-04 19:38 ` Patrick Mochel
2002-06-04 19:42 ` David S. Miller
2002-06-04 20:56 ` Tom Rini
2002-06-04 21:10 ` Patrick Mochel
2002-06-04 21:14 ` David S. Miller
2002-06-04 21:14 ` Patrick Mochel
2002-06-04 21:23 ` David S. Miller
2002-06-04 21:29 ` Patrick Mochel
2002-06-04 21:34 ` David S. Miller
2002-06-04 22:03 ` Patrick Mochel
2002-06-04 22:06 ` Patrick Mochel
2002-06-05 14:23 ` Ivan Kokshaysky
2002-06-05 22:29 ` David S. Miller
2002-06-06 0:01 ` Patrick Mochel
2002-06-06 13:22 ` Ivan Kokshaysky
2002-06-23 17:03 ` Jan-Benedict Glaw
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=20020604.111337.51699424.davem@redhat.com \
--to=davem@redhat.com \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@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