[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180925204801.6182.73167.stgit@localhost.localdomain>
Date: Tue, 25 Sep 2018 13:52:56 -0700
From: Alexander Duyck <alexander.h.duyck@...ux.intel.com>
To: linux-kernel@...r.kernel.org, linux-nvdimm@...ts.01.org
Cc: vishal.l.verma@...el.com, dan.j.williams@...el.com,
dave.jiang@...el.com, zwisler@...nel.org
Subject: [PATCH 0/2] Minor fixups for nd_device_register
This patch series addresses a couple minor issues in nd_device_register.
The first patch resolves an issue in which we weren't holding the parent
lock so it is possible the parent could have been released prior to us
taking care of initializing the device via the asynchronous init.
The second patch moves the initialization of the device node to the
earliest point where we can do it. By doing this we can avoid repeatedly
updating the node on each uevent.
---
Alexander Duyck (2):
nvdimm: Hold reference on parent while scheduling async init
nvdimm: Set device node in nd_device_register
drivers/nvdimm/bus.c | 20 ++++++++++++++------
1 file changed, 14 insertions(+), 6 deletions(-)
--
Powered by blists - more mailing lists