From: Jonathan Cameron <jic23@kernel.org>
To: kbuild test robot <fengguang.wu@intel.com>,
Andreas Dannenberg <dannenberg@ti.com>
Cc: kbuild-all@01.org, Felipe Balbi <balbi@ti.com>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: light: fix platform_no_drv_owner.cocci warnings
Date: Mon, 31 Aug 2015 16:11:38 +0100 [thread overview]
Message-ID: <55E46EAA.2020107@kernel.org> (raw)
In-Reply-To: <20150830084657.GA58183@lkp-sb04>
On 30/08/15 09:46, kbuild test robot wrote:
> drivers/iio/light/opt3001.c:796: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
>
> CC: Andreas Dannenberg <dannenberg@ti.com>
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
Applied to the togreg branch of iio.git - will be initially pushed out as testing for
the autobuilders to play with it.
Thanks,
Jonathan
> ---
>
> opt3001.c | 1 -
> 1 file changed, 1 deletion(-)
>
> --- a/drivers/iio/light/opt3001.c
> +++ b/drivers/iio/light/opt3001.c
> @@ -793,7 +793,6 @@ static struct i2c_driver opt3001_driver
> .driver = {
> .name = "opt3001",
> .of_match_table = of_match_ptr(opt3001_of_match),
> - .owner = THIS_MODULE,
> },
> };
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-08-31 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201508301646.pc4xpAKe%fengguang.wu@intel.com>
2015-08-30 8:46 ` [PATCH] iio: light: fix platform_no_drv_owner.cocci warnings kbuild test robot
2015-08-31 15:11 ` Jonathan Cameron [this message]
[not found] <201509221047.iRuxezuD%fengguang.wu@intel.com>
[not found] ` <20150922022148.GA7041@lkp-sb04>
2015-09-23 19:06 ` Jonathan Cameron
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=55E46EAA.2020107@kernel.org \
--to=jic23@kernel.org \
--cc=balbi@ti.com \
--cc=dannenberg@ti.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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).