From: Yang Li <yang.lee@linux.alibaba.com>
To: davem@davemloft.net
Cc: kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Yang Li <yang.lee@linux.alibaba.com>
Subject: [PATCH -next 2/2] tsnep: fix platform_no_drv_owner.cocci warning
Date: Wed, 24 Nov 2021 10:36:24 +0800 [thread overview]
Message-ID: <1637721384-70836-2-git-send-email-yang.lee@linux.alibaba.com> (raw)
In-Reply-To: <1637721384-70836-1-git-send-email-yang.lee@linux.alibaba.com>
Remove .owner field if calls are used which set it automatically
Eliminate the following coccicheck warning:
./drivers/net/ethernet/engleder/tsnep_main.c:1263:3-8: No need to set
.owner here. The core will do it.
Reported-by: Abaci Robot <abaci@linux.alibaba.com>
Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
---
drivers/net/ethernet/engleder/tsnep_main.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/net/ethernet/engleder/tsnep_main.c b/drivers/net/ethernet/engleder/tsnep_main.c
index c48e8ea..3d0408e 100644
--- a/drivers/net/ethernet/engleder/tsnep_main.c
+++ b/drivers/net/ethernet/engleder/tsnep_main.c
@@ -1260,7 +1260,6 @@ static int tsnep_remove(struct platform_device *pdev)
static struct platform_driver tsnep_driver = {
.driver = {
.name = TSNEP,
- .owner = THIS_MODULE,
.of_match_table = of_match_ptr(tsnep_of_match),
},
.probe = tsnep_probe,
--
1.8.3.1
next prev parent reply other threads:[~2021-11-24 2:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 2:36 [PATCH -next 1/2] tsnep: fix resource_size.cocci warnings Yang Li
2021-11-24 2:36 ` Yang Li [this message]
2021-11-24 20:32 ` [PATCH -next 2/2] tsnep: fix platform_no_drv_owner.cocci warning Gerhard Engleder
2021-11-25 2:11 ` Jakub Kicinski
2021-11-24 20:28 ` [PATCH -next 1/2] tsnep: fix resource_size.cocci warnings Gerhard Engleder
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=1637721384-70836-2-git-send-email-yang.lee@linux.alibaba.com \
--to=yang.lee@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).