From: kernel test robot <lkp@intel.com>
To: Lars Poeschel <poeschel@lemonage.de>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Miguel Ojeda <ojeda@kernel.org>,
Miguel Ojeda Sandonis <miguel.ojeda.sandonis@gmail.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH] auxdisplay: fix platform_no_drv_owner.cocci warnings
Date: Wed, 11 Nov 2020 17:25:59 +0800 [thread overview]
Message-ID: <20201111092559.GA67395@c88ae2e89e59> (raw)
In-Reply-To: <202011111755.9Uwp2gF6-lkp@intel.com>
From: kernel test robot <lkp@intel.com>
drivers/auxdisplay/lcd2s.c:373: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
Fixes: 8c9108d014c5 ("auxdisplay: add a driver for lcd2s character display")
CC: Lars Poeschel <poeschel@lemonage.de>
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 3e14f70c05cda4794901ed8f976de3a88deebcc0
commit: 8c9108d014c5bd0f0da2e3544eb45dc56a6da92b [2648/5074] auxdisplay: add a driver for lcd2s character display
lcd2s.c | 1 -
1 file changed, 1 deletion(-)
--- a/drivers/auxdisplay/lcd2s.c
+++ b/drivers/auxdisplay/lcd2s.c
@@ -370,7 +370,6 @@ MODULE_DEVICE_TABLE(of, lcd2s_of_table);
static struct i2c_driver lcd2s_i2c_driver = {
.driver = {
.name = "lcd2s",
- .owner = THIS_MODULE,
#ifdef CONFIG_OF
.of_match_table = of_match_ptr(lcd2s_of_table),
#endif
next prev parent reply other threads:[~2020-11-11 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 9:25 [linux-next:master 2648/5074] drivers/auxdisplay/lcd2s.c:373:3-8: No need to set .owner here. The core will do it kernel test robot
2020-11-11 9:25 ` kernel test robot [this message]
2020-11-14 8:54 ` [PATCH] auxdisplay: fix platform_no_drv_owner.cocci warnings Miguel Ojeda
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=20201111092559.GA67395@c88ae2e89e59 \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=poeschel@lemonage.de \
/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