LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Michael Schmitz <schmitzmic@gmail.com>,
Finn Thain <fthain@telegraphics.com.au>,
"Linux/m68k" <linux-m68k@lists.linux-m68k.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nubus: Unconditionally register bus type
Date: Tue, 8 May 2018 09:07:27 +0200 [thread overview]
Message-ID: <CAMuHMdUAWfmiaZG7snEQRL1N-w69NuSYzeoQgQosQRf_JTZ5OQ@mail.gmail.com> (raw)
In-Reply-To: <20180508070037.GA4792@kroah.com>
Hi Greg,
On Tue, May 8, 2018 at 9:00 AM, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
> On Mon, May 07, 2018 at 09:51:12AM +1200, Michael Schmitz wrote:
>> the BUG() was triggered by loading a Mac Nubus network card module on
>> a multiplatform kernel running on an Amiga machine. Up to Finn's Nubus
>> core rewrite (this February), we've seen no errors. Since then, Nubus
>> drivers fail to register because the Nubus bus is only registered on
>> Macs.
>>
>> Can't see link order involved here at all.
>
> The link order is totally involved here :)
>
> Link order determines the order in which init calls are run, so you need
> to ensure that your bus code comes before any drivers that use that bus
> code in link order. That way, at init time, your bus is created first,
> preventing this type of error to happen.
The issue here is not due to link ordering, but due to the bus not being
registered on a system that doesn't have that particular bus.
Akin to booting a kernel on an old PC without PCI, and loading a driver
module for a PCI network card. I guess that doesn't crash (because no one
has a PC without PCI anymore? ;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2018-05-08 7:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 1:47 Finn Thain
2018-05-06 4:55 ` Greg Kroah-Hartman
2018-05-06 6:00 ` Finn Thain
2018-05-06 20:20 ` Greg Kroah-Hartman
2018-05-06 21:51 ` Michael Schmitz
2018-05-08 7:00 ` Greg Kroah-Hartman
2018-05-08 7:07 ` Geert Uytterhoeven [this message]
2018-05-08 7:25 ` Greg Kroah-Hartman
2018-05-08 7:35 ` Geert Uytterhoeven
2018-05-08 7:41 ` Greg Kroah-Hartman
2018-05-08 8:01 ` Michael Schmitz
2018-05-06 23:57 ` Finn Thain
2018-05-07 12:53 ` Geert Uytterhoeven
2018-05-07 14:45 ` Greg Kroah-Hartman
2018-05-08 6:28 ` Geert Uytterhoeven
2018-05-07 23:44 ` Finn Thain
2018-05-08 6:32 ` Geert Uytterhoeven
2018-05-08 7:59 ` Finn Thain
2018-05-08 7:01 ` Greg Kroah-Hartman
2018-05-06 1:47 Finn Thain
[not found] <5aee5ede.1c69fb81.353b4.5021SMTPIN_ADDED_MISSING@mx.google.com>
2018-05-08 7:39 ` Geert Uytterhoeven
2018-05-08 8:27 ` Finn Thain
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=CAMuHMdUAWfmiaZG7snEQRL1N-w69NuSYzeoQgQosQRf_JTZ5OQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=fthain@telegraphics.com.au \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=schmitzmic@gmail.com \
--subject='Re: [PATCH] nubus: Unconditionally register bus type' \
/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
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).