From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Michael Schmitz <schmitzmic@gmail.com>
Cc: Finn Thain <fthain@telegraphics.com.au>,
Geert Uytterhoeven <geert@linux-m68k.org>,
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:00:37 +0200 [thread overview]
Message-ID: <20180508070037.GA4792@kroah.com> (raw)
In-Reply-To: <CAOmrzk+bY5wUxJhNAwO-pf+O--HiqJ63rB3BmxRsY8qq_PeLmw@mail.gmail.com>
On Mon, May 07, 2018 at 09:51:12AM +1200, Michael Schmitz wrote:
> Hi Greg,
>
> 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.
> Safeguarding against this bug could be done by checking a
> bus-is-registered flag, or checking what machine model the kernel runs
> on. Simply registering the Nubus bus driver regardless of machine
> model seemed the easiest way.
If you really have this problem due to link ordering issues not being
able to be worked around (due to different directories and the like),
then put a "bus is registered" flag in your bus code. That will solve
the initial BUG_ON() problem, and you should return an error that allows
the driver code to probe your driver later on after your bus is enabled.
Hope this helps,
greg k-h
next prev parent reply other threads:[~2018-05-08 7:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 1:47 [PATCH] nubus: Unconditionally register bus type 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 [this message]
2018-05-08 7:07 ` Geert Uytterhoeven
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
[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
-- strict thread matches above, loose matches on Subject: below --
2018-05-06 1:47 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=20180508070037.GA4792@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=schmitzmic@gmail.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