From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751748AbdKYBDR (ORCPT ); Fri, 24 Nov 2017 20:03:17 -0500 Received: from kvm5.telegraphics.com.au ([98.124.60.144]:40476 "EHLO kvm5.telegraphics.com.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751053AbdKYBDP (ORCPT ); Fri, 24 Nov 2017 20:03:15 -0500 Date: Sat, 25 Nov 2017 12:03:12 +1100 (AEDT) From: Finn Thain To: Greg Kroah-Hartman cc: Geert Uytterhoeven , linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 13/13] nubus: Add support for the driver model In-Reply-To: <20171124082428.GA21608@kroah.com> Message-ID: References: <7f84ae0e2d6195ce0a4af1963d5ac15ff02a4749.1510960933.git.fthain@telegraphics.com.au> <20171118102123.GC8368@kroah.com> <20171123080449.GB490@kroah.com> <20171124082428.GA21608@kroah.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. --