Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp1000664imm; Fri, 17 Aug 2018 10:06:02 -0700 (PDT) X-Google-Smtp-Source: AA+uWPzmHzEE0GgYbIXOfpZ4T/FhMS+OlBpEIcadCzA5IQPD5GVtESgLcwq90NUsjKZZF1x8oduA X-Received: by 2002:a62:591a:: with SMTP id n26-v6mr37564078pfb.94.1534525561955; Fri, 17 Aug 2018 10:06:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1534525561; cv=none; d=google.com; s=arc-20160816; b=FxdA+WURgYNuQIsrGjyM3IdHX+dnxJ9HDNJGUE+TXzgxikygNjs4dQUfjNGY3IMy0K iQrAOSn5QL48cpZS0bmh7ENKPoo6AzgeVAgyEy570mRMh2p87x99/6TjNqFAPrCSLm9C tvG9u1QGIRrDsDG2wBMh+D2vdWJLdvATyK6n8f/0/n6IGVEO8HsX166F4WxJxmvGpgOG 3d8LRw3p+c0pGQhfSmQt1+ugYa3OuwZ5x3hot3avC9EJp3VD+Sn8utLWujbYsU6glao2 fw1y0jJHKZqq1KDd03Cb65Hxj3TuE0aTIthI8S80FwHVFhaKIGGuQhw/YFC0d9mE7UIe 4qOg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=0O5jOTZDmc6UNyiUQbtBoK/rCEglm8TvaZSvrFpfA50=; b=002kmnn3BCV1RH0QsNsLXBYaq3BgahWBBKEZSIf90h7aiagpD6CY1IdZgatjwLGa+p SHMG/5euLWOlC2pAEv3XdRWu/ZrHbZamKhKQ/fupWrtwsTZYaQ9yfGi2PATwbS8IR72W 0BOnjyeD8mzWr4pjXCF+7fsVXb3Au5DsBZZWlG+DYn2VI/7XQPRFSksBzQI6MclbOsq1 YzJutOPhW8OLAFiZhWslDSh/1dKM7byN2KWMJlGW75GV/cdBQZkpcim9vRj2Tvktpnvr PBNYdr32QVfn4ptbXsU7D+xhMgWCRWq7wo/PStximlW/vu9Hoz042ctuGmeZXnLypil/ Sa+g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v21-v6si2680350plo.397.2018.08.17.10.05.44; Fri, 17 Aug 2018 10:06:01 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728073AbeHQUGv (ORCPT + 99 others); Fri, 17 Aug 2018 16:06:51 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:55860 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727778AbeHQUGv (ORCPT ); Fri, 17 Aug 2018 16:06:51 -0400 Received: from localhost (unknown [194.244.16.108]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id 51CBFCAA; Fri, 17 Aug 2018 17:02:42 +0000 (UTC) Date: Fri, 17 Aug 2018 19:02:39 +0200 From: Greg Kroah-Hartman To: David Hildenbrand Cc: Heiko Carstens , Michal Hocko , "Rafael J. Wysocki" , Benjamin Herrenschmidt , Linux Memory Management List , Paul Mackerras , linux-s390@vger.kernel.org, sthemmin@microsoft.com, Pavel Tatashin , ACPI Devel Maling List , David Rientjes , xen-devel@lists.xenproject.org, Len Brown , haiyangz@microsoft.com, Dan Williams , Vitaly Kuznetsov , Vlastimil Babka , osalvador@suse.de, "Rafael J. Wysocki" , Linux Kernel Mailing List , Martin Schwidefsky , devel@linuxdriverproject.org, Andrew Morton , linuxppc-dev Subject: Re: [PATCH RFC 1/2] drivers/base: export lock_device_hotplug/unlock_device_hotplug Message-ID: <20180817170239.GF24945@kroah.com> References: <20180817075901.4608-1-david@redhat.com> <20180817075901.4608-2-david@redhat.com> <20180817084146.GB14725@kroah.com> <5a5d73e9-e4aa-ffed-a2e3-8aef64e61923@redhat.com> <42df9062-f647-3ad6-5a07-be2b99531119@redhat.com> <20180817100604.GA18164@kroah.com> <4ac624be-d2d6-5975-821f-b20a475781dc@redhat.com> <20180817112850.GB3565@osiris> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 17, 2018 at 01:56:35PM +0200, David Hildenbrand wrote: > E.g. When adding the memory block devices, we know that there won't be a > driver to attach to (as there are no drivers for the "memory" subsystem) > - the bus_probe_device() function that takes the device_lock() could > pretty much be avoided for that case. But burying such special cases > down in core driver code definitely won't make locking related to memory > hotplug easier. You don't have to have a driver for a device if you don't want to, or you can just have a default one for all memory devices if you somehow need it. No reason to not do this if it makes things easier for you. thanks, greg k-h