From: Finn Thain <fthain@telegraphics.com.au>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 13/13] nubus: Add support for the driver model
Date: Sat, 25 Nov 2017 12:03:12 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LNX.2.00.1711251144190.3@nippy.intranet> (raw)
In-Reply-To: <20171124082428.GA21608@kroah.com>
On Fri, 24 Nov 2017, Greg Kroah-Hartman wrote:
> > >
> > > But what happens when the bus code is unloaded if it is built as a
> > > module? The devices will be removed then. Or they should be.
> > >
> >
> > This bus driver is not a module.
>
> It can not be built as a module ever?
>
That's right:
$ cat arch/m68k/Kconfig.bus
...
config NUBUS
bool
depends on MAC
default y
I don't plan to convert this bus driver to a module, but this patch series
would make that conversion more difficult, should it happen in future.
Therefore I plan to revise this submission to avoid or remove the existing
global nubus_boards list, because the use of this list means that a
hypothetical device_put() call is not allowable.
You may wish to disregard this submission.
Thanks.
--
next prev parent reply other threads:[~2017-11-25 1:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-18 2:30 [PATCH v2 00/13] Modernization and fixes for NuBus subsystem Finn Thain
2017-11-18 2:30 ` [PATCH v2 04/13] nubus: Fix log spam Finn Thain
2017-11-18 2:30 ` [PATCH v2 02/13] nubus: Fix up header split Finn Thain
2017-11-18 2:30 ` [PATCH v2 10/13] nubus: Rework /proc/bus/nubus/s/ implementation Finn Thain
2017-11-18 2:30 ` [PATCH v2 07/13] nubus: Remove redundant code Finn Thain
2017-11-18 2:30 ` [PATCH v2 06/13] nubus: Call proc_mkdir() not more than once per slot directory Finn Thain
2017-11-18 2:30 ` [PATCH v2 09/13] nubus: Generalize block resource handling Finn Thain
2017-11-18 2:30 ` [PATCH v2 11/13] nubus: Rename struct nubus_dev Finn Thain
2017-11-18 2:30 ` [PATCH v2 13/13] nubus: Add support for the driver model Finn Thain
2017-11-18 10:21 ` Greg Kroah-Hartman
2017-11-20 1:01 ` Finn Thain
2017-11-23 0:24 ` Finn Thain
2017-11-23 8:04 ` Greg Kroah-Hartman
2017-11-23 23:40 ` Finn Thain
2017-11-24 8:24 ` Greg Kroah-Hartman
2017-11-25 1:03 ` Finn Thain [this message]
2017-11-18 2:30 ` [PATCH v2 12/13] nubus: Add expansion_type values for various Mac models Finn Thain
2017-11-18 2:30 ` [PATCH v2 05/13] nubus: Validate slot resource IDs Finn Thain
2017-11-18 2:30 ` [PATCH v2 03/13] nubus: Use static functions where possible Finn Thain
2017-11-18 2:30 ` [PATCH v2 08/13] nubus: Clean up whitespace Finn Thain
2017-11-18 2:30 ` [PATCH v2 01/13] nubus: Avoid array underflow and overflow 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=alpine.LNX.2.00.1711251144190.3@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).