From: "David S. Miller" <davem@redhat.com>
To: ink@jurassic.park.msu.ru
Cc: mochel@osdl.org, anton@samba.org, linux-kernel@vger.kernel.org
Subject: Re: [2.5.19] Oops during PCI scan on Alpha
Date: Wed, 05 Jun 2002 15:29:59 -0700 (PDT) [thread overview]
Message-ID: <20020605.152959.98861473.davem@redhat.com> (raw)
In-Reply-To: <20020605182316.B3437@jurassic.park.msu.ru>
From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Date: Wed, 5 Jun 2002 18:23:16 +0400
On Tue, Jun 04, 2002 at 03:03:33PM -0700, Patrick Mochel wrote:
> -subsys_initcall(pci_driver_init);
> +postcore_initcall(pci_driver_init);
Fine, but my main objection was to pci_driver_init being an initcall
in general, no matter in what level. With current code we may have
pci_bus_type registered on a machine without PCI bus.
Real life example: jensen running generic alpha kernel.
Ok, then we should have pci_driver_init called from the beginning
of pcibios_init if PCI controllers are found.
next prev parent reply other threads:[~2002-06-05 22:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 20:06 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
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 [this message]
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=20020605.152959.98861473.davem@redhat.com \
--to=davem@redhat.com \
--cc=anton@samba.org \
--cc=ink@jurassic.park.msu.ru \
--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
all inboxes | Powered by JetHome®