From: David Kershner Date: Tue, 28 Mar 2017 13:34:29 +0000 (-0400) Subject: staging: unisys: visorbus: remove invalid comment, we are one driver. X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=d337822efb722fab6096b164b4b1a9d10954edf5;p=GitHub%2Fmoto-9609%2Fandroid_kernel_motorola_exynos9610.git staging: unisys: visorbus: remove invalid comment, we are one driver. Removed a comment that was describing the relationship between the visorchipset driver and the visorbus driver. Since they are now one driver the comment no longer makes sense. Signed-off-by: David Kershner Reviewed-by: Reviewed-by: Tim Sell Signed-off-by: Greg Kroah-Hartman --- diff --git a/drivers/staging/unisys/visorbus/visorbus_main.c b/drivers/staging/unisys/visorbus/visorbus_main.c index bb1b6a0bf5de..b99adaaeee15 100644 --- a/drivers/staging/unisys/visorbus/visorbus_main.c +++ b/drivers/staging/unisys/visorbus/visorbus_main.c @@ -1227,14 +1227,6 @@ initiate_chipset_device_pause_resume(struct visor_device *dev, bool is_pause) return; } - /* - * Note that even though both drv->pause() and drv->resume - * specify a callback function, it is NOT necessary for us to - * increment our local module usage count. Reason is, there - * is already a linkage dependency between child function - * drivers and visorbus, so it is already IMPOSSIBLE to unload - * visorbus while child function drivers are still running. - */ if (is_pause) { if (!drv->pause) { (*notify_func)(dev, -EINVAL);