dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Thierry Reding <treding@nvidia.com>
Cc: "Vincent Palatin" <vpalatin@chromium.org>,
	dri-devel@lists.freedesktop.org,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	kbuild-all@01.org,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Gustavo Padovan" <gustavo.padovan@collabora.co.uk>
Subject: [PATCH] drm/bridge: fix platform_no_drv_owner.cocci warnings
Date: Fri, 21 Aug 2015 19:05:39 +0800	[thread overview]
Message-ID: <20150821110539.GA153903@ivytown2> (raw)
In-Reply-To: <201508211922.3S711l5f%fengguang.wu@intel.com>

drivers/gpu/drm/bridge/parade-ps8622.c:671:3-8: No need to set .owner here. The core will do it.

 Remove .owner field if calls are used which set it automatically

Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci

Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---

 parade-ps8622.c |    1 -
 1 file changed, 1 deletion(-)

--- a/drivers/gpu/drm/bridge/parade-ps8622.c
+++ b/drivers/gpu/drm/bridge/parade-ps8622.c
@@ -668,7 +668,6 @@ static struct i2c_driver ps8622_driver =
 	.remove		= ps8622_remove,
 	.driver		= {
 		.name	= "ps8622",
-		.owner	= THIS_MODULE,
 		.of_match_table = ps8622_devices,
 	},
 };
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

       reply	other threads:[~2015-08-21 11:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201508211922.3S711l5f%fengguang.wu@intel.com>
2015-08-21 11:05 ` kbuild test robot [this message]
2015-09-04  9:43   ` [PATCH] drm/bridge: fix platform_no_drv_owner.cocci warnings Thierry Reding
2015-08-21 11:05 ` kbuild test robot
2015-09-04  9:43   ` Thierry Reding
2015-10-16 13:52 [RFC 2/2] drm/bridge: Add I2C based driver for ps8640 bridge kbuild test robot
2015-10-16 12:15 ` CK Hu
2015-10-16 13:52   ` [PATCH] drm/bridge: fix platform_no_drv_owner.cocci warnings kbuild test robot
  -- strict thread matches above, loose matches on Subject: below --
2016-10-26 16:58 [drm-intel:topic/drm-misc 3/3] drivers/gpu/drm/bridge/sil-sii8620.c:1556:3-8: No need to set .owner here. The core will do it kbuild test robot
2016-10-26 16:58 ` [PATCH] drm/bridge: fix platform_no_drv_owner.cocci warnings kbuild test robot
2017-08-03 19:36 [PATCH 1/2] drm/bridge: add Silicon Image SiI9234 driver kbuild test robot
     [not found] ` <1501746323-5254-2-git-send-email-m.purski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2017-08-03 19:36   ` [PATCH] drm/bridge: fix platform_no_drv_owner.cocci warnings kbuild test robot
2018-04-27  9:39 [PATCH v4 1/3] drm/bridge: add support for sn65dsi86 bridge driver Sandeep Panda
     [not found] ` <1524821982-2778-2-git-send-email-spanda-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-04-30  1:50   ` [PATCH] drm/bridge: fix platform_no_drv_owner.cocci warnings kbuild test robot

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=20150821110539.GA153903@ivytown2 \
    --to=fengguang.wu@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert@linux-m68k.org \
    --cc=gustavo.padovan@collabora.co.uk \
    --cc=kbuild-all@01.org \
    --cc=treding@nvidia.com \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=vpalatin@chromium.org \
    /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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).