From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [PATCH] omap: mcasp: fix platform_no_drv_owner.cocci warnings
Date: Fri, 20 Mar 2020 10:16:22 +0800 [thread overview]
Message-ID: <20200320021622.GA45729@9f26ed696032> (raw)
In-Reply-To: <202003201017.II8le8jJ%lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
From: kbuild test robot <lkp@intel.com>
sound/soc/ti/omap-mcasp.c:691: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: 912e5fb4149f ("omap: mcasp: add omap-mcasp.* and add to Kconfig, Makefile")
CC: Andrey Utkin <andrey_utkin@fastmail.com>
Signed-off-by: kbuild test robot <lkp@intel.com>
---
tree: https://github.com/omap-audio/linux-audio peter/linux-next-wip
head: 6ac31c0a3cce3aa9f6e4551095fc0e64c7ae58c0
commit: 912e5fb4149f3374bcb878634622866a8f71205d [70/82] omap: mcasp: add omap-mcasp.* and add to Kconfig, Makefile
omap-mcasp.c | 1 -
1 file changed, 1 deletion(-)
--- a/sound/soc/ti/omap-mcasp.c
+++ b/sound/soc/ti/omap-mcasp.c
@@ -688,7 +688,6 @@ MODULE_DEVICE_TABLE(of, omap_mcasp_of_ma
static struct platform_driver omap_mcasp_driver = {
.driver = {
.name = "omap-mcasp",
- .owner = THIS_MODULE,
.of_match_table = omap_mcasp_of_match,
},
.probe = asoc_mcasp_probe,
next prev parent reply other threads:[~2020-03-20 2:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 2:16 [omap-audio:peter/linux-next-wip 70/82] sound/soc/ti/omap-mcasp.c:691:3-8: No need to set .owner here. The core will do it kbuild test robot
2020-03-20 2:16 ` kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-11 0:13 [omap-audio:peter/linux-next-wip 58/63] sound/soc/ti/omap-mcasp.c:630:2-9: line 630 is redundant because platform_get_irq() already prints an error kernel test robot
2021-04-11 0:13 ` [PATCH] omap: mcasp: fix platform_no_drv_owner.cocci warnings kernel test robot
2020-12-12 21:00 [omap-audio:peter/linux-next-wip 79/94] sound/soc/ti/omap-mcasp.c:630:2-9: line 630 is redundant because platform_get_irq() already prints an error kernel test robot
2020-12-12 21:00 ` [PATCH] omap: mcasp: fix platform_no_drv_owner.cocci warnings kernel test robot
2020-05-09 15:20 [omap-audio:peter/linux-next-wip 76/89] sound/soc/ti/omap-mcasp.c:691:3-8: No need to set .owner here. The core will do it kbuild test robot
2020-05-09 15:20 ` [PATCH] omap: mcasp: fix platform_no_drv_owner.cocci warnings kbuild test robot
2020-03-03 5:35 [omap-audio:peter/linux-next-wip 88/98] sound/soc/ti/omap-mcasp.c:691:3-8: No need to set .owner here. The core will do it kbuild test robot
2020-03-03 5:35 ` [PATCH] omap: mcasp: fix platform_no_drv_owner.cocci warnings kbuild test robot
2020-02-04 14:03 [omap-audio:peter/linux-next-wip 86/97] sound/soc/ti/omap-mcasp.c:691:3-8: No need to set .owner here. The core will do it kbuild test robot
2020-02-04 14:03 ` [PATCH] omap: mcasp: fix platform_no_drv_owner.cocci warnings kbuild test robot
2020-01-12 9:46 [omap-audio:peter/linux-next-wip 118/125] sound/soc/ti/omap-mcasp.c:691:3-8: No need to set .owner here. The core will do it kbuild test robot
2020-01-12 9:46 ` [PATCH] omap: mcasp: 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=20200320021622.GA45729@9f26ed696032 \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.