Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753703AbbGJIFJ (ORCPT ); Fri, 10 Jul 2015 04:05:09 -0400 Received: from mail-qg0-f49.google.com ([209.85.192.49]:36197 "EHLO mail-qg0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753628AbbGJIEw (ORCPT ); Fri, 10 Jul 2015 04:04:52 -0400 MIME-Version: 1.0 X-Originating-IP: [80.15.154.113] In-Reply-To: <1436510279-5682-1-git-send-email-k.kozlowski@samsung.com> References: <1436510279-5682-1-git-send-email-k.kozlowski@samsung.com> Date: Fri, 10 Jul 2015 10:04:51 +0200 Message-ID: Subject: Re: [PATCH] vfio: Drop owner assignment from platform_driver From: Baptiste Reynal To: Krzysztof Kozlowski Cc: Alex Williamson , "open list:VFIO PLATFORM DRIVER" , open list Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1301 Lines: 39 Thanks for the point Krzysztof. Acked-by: Baptiste Reynal On Fri, Jul 10, 2015 at 8:37 AM, Krzysztof Kozlowski wrote: > platform_driver does not need to set an owner because > platform_driver_register() will set it. > > Signed-off-by: Krzysztof Kozlowski > > --- > > The coccinelle script which generated the patch was sent here: > http://www.spinics.net/lists/kernel/msg2029903.html > --- > drivers/vfio/platform/vfio_platform.c | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/drivers/vfio/platform/vfio_platform.c b/drivers/vfio/platform/vfio_platform.c > index cef645c83996..09a8caa4eda9 100644 > --- a/drivers/vfio/platform/vfio_platform.c > +++ b/drivers/vfio/platform/vfio_platform.c > @@ -91,7 +91,6 @@ static struct platform_driver vfio_platform_driver = { > .remove = vfio_platform_remove, > .driver = { > .name = "vfio-platform", > - .owner = THIS_MODULE, > }, > }; > > -- > 1.9.1 > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/