From: kbuild test robot <lkp@intel.com>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Olof Johansson <olof@lixom.net>, Gene Chen <gene.chen@intel.com>,
Benson Leung <bleung@chromium.org>,
Aaron Durbin <adurbin@chromium.org>,
Filipe Brandenburger <filbranden@chromium.org>,
Ben Zhang <benzh@chromium.org>,
Olof Johansson <olofj@chromium.org>,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Subject: [PATCH] platform/chrome: pstore: fix platform_no_drv_owner.cocci warnings
Date: Mon, 15 Feb 2016 17:00:11 +0800 [thread overview]
Message-ID: <20160215090011.GA87856@roam> (raw)
In-Reply-To: <1455523133-6939-3-git-send-email-enric.balletbo@collabora.com>
drivers/platform/chrome/chromeos_pstore.c:85: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: Aaron Durbin <adurbin@chromium.org>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
chromeos_pstore.c | 1 -
1 file changed, 1 deletion(-)
--- a/drivers/platform/chrome/chromeos_pstore.c
+++ b/drivers/platform/chrome/chromeos_pstore.c
@@ -82,7 +82,6 @@ MODULE_DEVICE_TABLE(acpi, cros_ramoops_a
static struct platform_driver chromeos_ramoops_acpi = {
.driver = {
.name = "chromeos_pstore",
- .owner = THIS_MODULE,
.acpi_match_table = ACPI_PTR(cros_ramoops_acpi_match),
},
};
next prev parent reply other threads:[~2016-02-15 9:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 7:58 [PATCH 0/3] platform/chrome: upstream changes Enric Balletbo i Serra
2016-02-15 7:58 ` [PATCH 1/3] platform/chrome: chromeos_laptop: Add Leon Touch Enric Balletbo i Serra
2016-05-03 5:38 ` Benson Leung
2016-02-15 7:58 ` [PATCH 2/3] platform/chrome: pstore: probe for ramoops buffer using acpi Enric Balletbo i Serra
2016-02-15 9:00 ` kbuild test robot
2016-02-15 9:00 ` kbuild test robot [this message]
2016-02-15 7:58 ` [PATCH 3/3] platform/chrome: pstore: Move to larger record size Enric Balletbo i Serra
2016-05-03 5:41 ` Benson Leung
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=20160215090011.GA87856@roam \
--to=lkp@intel.com \
--cc=adurbin@chromium.org \
--cc=benzh@chromium.org \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=filbranden@chromium.org \
--cc=gene.chen@intel.com \
--cc=gustavo.padovan@collabora.co.uk \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=olofj@chromium.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