From: Robert Baldyga <r.baldyga@samsung.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Samuel Ortiz <sameo@linux.intel.com>,
Lauro Ramos Venancio <lauro.venancio@openbossa.org>,
Aloisio Almeida Jr <aloisio.almeida@openbossa.org>,
linux-nfc@lists.01.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] nfc: s3fwrn5: fix platform_no_drv_owner.cocci warnings
Date: Wed, 07 Oct 2015 08:50:49 +0200 [thread overview]
Message-ID: <5614C0C9.2040703@samsung.com> (raw)
In-Reply-To: <20151007004021.GA130523@xian>
On 10/07/2015 02:40 AM, kbuild test robot wrote:
> drivers/nfc/s3fwrn5/i2c.c:293: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: Robert Baldyga <r.baldyga@samsung.com>
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
Acked-by: Robert Baldyga <r.baldyga@samsung.com>
Thanks!
Robert Baldyga
> ---
>
> i2c.c | 1 -
> 1 file changed, 1 deletion(-)
>
> --- a/drivers/nfc/s3fwrn5/i2c.c
> +++ b/drivers/nfc/s3fwrn5/i2c.c
> @@ -290,7 +290,6 @@ MODULE_DEVICE_TABLE(of, of_s3fwrn5_i2c_m
>
> static struct i2c_driver s3fwrn5_i2c_driver = {
> .driver = {
> - .owner = THIS_MODULE,
> .name = S3FWRN5_I2C_DRIVER_NAME,
> .of_match_table = of_match_ptr(of_s3fwrn5_i2c_match),
> },
>
prev parent reply other threads:[~2015-10-07 6:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201510070819.IsIYdbtW%fengguang.wu@intel.com>
2015-10-07 0:40 ` [PATCH] nfc: s3fwrn5: fix platform_no_drv_owner.cocci warnings kbuild test robot
2015-10-07 6:50 ` Robert Baldyga [this message]
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=5614C0C9.2040703@samsung.com \
--to=r.baldyga@samsung.com \
--cc=aloisio.almeida@openbossa.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=lauro.venancio@openbossa.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfc@lists.01.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sameo@linux.intel.com \
/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).