From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> To: Inki Dae <inki.dae@samsung.com>, Seung-Woo Kim <sw0312.kim@samsung.com>, Kyungmin Park <kyungmin.park@samsung.com>, David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>, Alim Akhtar <alim.akhtar@samsung.com> Cc: dri-devel@lists.freedesktop.org, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH 04/11] drm/exynos: g2d: drop driver owner initialization Date: Sat, 30 Mar 2024 21:33:08 +0100 [thread overview] Message-ID: <20240330-b4-module-owner-drm-exynos-v1-4-3fa30e2c7e5a@linaro.org> (raw) In-Reply-To: <20240330-b4-module-owner-drm-exynos-v1-0-3fa30e2c7e5a@linaro.org> Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> --- drivers/gpu/drm/exynos/exynos_drm_g2d.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/exynos/exynos_drm_g2d.c b/drivers/gpu/drm/exynos/exynos_drm_g2d.c index f3138423612e..3a3b2c00e400 100644 --- a/drivers/gpu/drm/exynos/exynos_drm_g2d.c +++ b/drivers/gpu/drm/exynos/exynos_drm_g2d.c @@ -1610,7 +1610,6 @@ struct platform_driver g2d_driver = { .remove_new = g2d_remove, .driver = { .name = "exynos-drm-g2d", - .owner = THIS_MODULE, .pm = pm_ptr(&g2d_pm_ops), .of_match_table = exynos_g2d_match, }, -- 2.34.1
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> To: Inki Dae <inki.dae@samsung.com>, Seung-Woo Kim <sw0312.kim@samsung.com>, Kyungmin Park <kyungmin.park@samsung.com>, David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>, Alim Akhtar <alim.akhtar@samsung.com> Cc: dri-devel@lists.freedesktop.org, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH 04/11] drm/exynos: g2d: drop driver owner initialization Date: Sat, 30 Mar 2024 21:33:08 +0100 [thread overview] Message-ID: <20240330-b4-module-owner-drm-exynos-v1-4-3fa30e2c7e5a@linaro.org> (raw) In-Reply-To: <20240330-b4-module-owner-drm-exynos-v1-0-3fa30e2c7e5a@linaro.org> Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> --- drivers/gpu/drm/exynos/exynos_drm_g2d.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/exynos/exynos_drm_g2d.c b/drivers/gpu/drm/exynos/exynos_drm_g2d.c index f3138423612e..3a3b2c00e400 100644 --- a/drivers/gpu/drm/exynos/exynos_drm_g2d.c +++ b/drivers/gpu/drm/exynos/exynos_drm_g2d.c @@ -1610,7 +1610,6 @@ struct platform_driver g2d_driver = { .remove_new = g2d_remove, .driver = { .name = "exynos-drm-g2d", - .owner = THIS_MODULE, .pm = pm_ptr(&g2d_pm_ops), .of_match_table = exynos_g2d_match, }, -- 2.34.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-03-30 20:33 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <CGME20240330203328epcas1p3132c85946c00e6a2432d3e23db6213e8@epcas1p3.samsung.com> 2024-03-30 20:33 ` [PATCH 00/11] drm/exynos: drop driver owner initialization Krzysztof Kozlowski 2024-03-30 20:33 ` Krzysztof Kozlowski 2024-03-30 20:33 ` [PATCH 01/11] drm/exynos: fimc: " Krzysztof Kozlowski 2024-03-30 20:33 ` Krzysztof Kozlowski 2024-03-30 20:33 ` [PATCH 02/11] drm/exynos: fimd: " Krzysztof Kozlowski 2024-03-30 20:33 ` Krzysztof Kozlowski 2024-03-30 20:33 ` [PATCH 03/11] drm/exynos: dsi: " Krzysztof Kozlowski 2024-03-30 20:33 ` Krzysztof Kozlowski 2024-03-30 20:33 ` Krzysztof Kozlowski [this message] 2024-03-30 20:33 ` [PATCH 04/11] drm/exynos: g2d: " Krzysztof Kozlowski 2024-03-30 20:33 ` [PATCH 05/11] drm/exynos: gsc: " Krzysztof Kozlowski 2024-03-30 20:33 ` Krzysztof Kozlowski 2024-03-30 20:33 ` [PATCH 06/11] drm/exynos: mic: " Krzysztof Kozlowski 2024-03-30 20:33 ` Krzysztof Kozlowski 2024-03-30 20:33 ` [PATCH 07/11] drm/exynos: rotator: " Krzysztof Kozlowski 2024-03-30 20:33 ` Krzysztof Kozlowski 2024-03-30 20:33 ` [PATCH 08/11] drm/exynos: scaler: " Krzysztof Kozlowski 2024-03-30 20:33 ` Krzysztof Kozlowski 2024-03-30 20:33 ` [PATCH 09/11] drm/exynos: vidi: " Krzysztof Kozlowski 2024-03-30 20:33 ` Krzysztof Kozlowski 2024-03-30 20:33 ` [PATCH 10/11] drm/exynos: hdmi: " Krzysztof Kozlowski 2024-03-30 20:33 ` Krzysztof Kozlowski 2024-03-30 20:33 ` [PATCH 11/11] drm/exynos: mixer: " Krzysztof Kozlowski 2024-03-30 20:33 ` Krzysztof Kozlowski 2024-04-05 5:11 ` [PATCH 00/11] drm/exynos: " 대인기/Tizen Platform Lab(SR)/삼성전자 2024-04-05 5:11 ` 대인기/Tizen Platform Lab(SR)/삼성전자
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20240330-b4-module-owner-drm-exynos-v1-4-3fa30e2c7e5a@linaro.org \ --to=krzysztof.kozlowski@linaro.org \ --cc=airlied@gmail.com \ --cc=alim.akhtar@samsung.com \ --cc=daniel@ffwll.ch \ --cc=dri-devel@lists.freedesktop.org \ --cc=inki.dae@samsung.com \ --cc=kyungmin.park@samsung.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-samsung-soc@vger.kernel.org \ --cc=sw0312.kim@samsung.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.