From: kbuild test robot <fengguang.wu@intel.com>
To: "Noralf Trønnes" <noralf@tronnes.org>
Cc: kbuild-all@01.org, linux-input@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: [input:next 1341/1344] drivers/input/touchscreen/ft6236.c:316:3-8: No need to set .owner here. The core will do it.
Date: Tue, 6 Oct 2015 09:35:30 +0800 [thread overview]
Message-ID: <201510060921.YCPWmDCt%fengguang.wu@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next
head: c65cf815653ec64e73d40819806c2d1aed91681e
commit: 92deea1350f9fa97a841d45cd1f8228d5e8aa667 [1341/1344] Input: add support for FocalTech FT6236 touchscreen controller
coccinelle warnings: (new ones prefixed by >>)
>> drivers/input/touchscreen/ft6236.c:316:3-8: No need to set .owner here. The core will do it.
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next reply other threads:[~2015-10-06 1:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 1:35 kbuild test robot [this message]
2015-10-06 1:35 ` [PATCH] Input: fix platform_no_drv_owner.cocci warnings kbuild test robot
2015-10-06 22:50 ` Dmitry Torokhov
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=201510060921.YCPWmDCt%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-input@vger.kernel.org \
--cc=noralf@tronnes.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).