From: kbuild test robot <lkp@intel.com>
To: Wang Yafei <wangyafei@goodix.com>
Cc: kbuild-all@01.org, Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Henrik Rydberg <rydberg@bitmath.org>,
linux-input@vger.kernel.org, andrew@goodix.com, mouse@goodix.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Input: Add driver for GOODiX GTx5 series touchsereen
Date: Mon, 19 Jun 2017 21:24:27 +0800 [thread overview]
Message-ID: <201706192107.ru8ophjW%fengguang.wu@intel.com> (raw)
In-Reply-To: <33339a02-dac7-9097-9ea4-3c12c7b84a59@goodix.com>
Hi Wang,
[auto build test WARNING on input/next]
[also build test WARNING on v4.12-rc5 next-20170619]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Wang-Yafei/Input-Add-driver-for-GOODiX-GTx5-series-touchsereen/20170619-200451
base: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next
coccinelle warnings: (new ones prefixed by >>)
>> drivers/input/touchscreen/goodix-ts-sunrise/goodix_gtx5_i2c.c:872:3-8: No need to set .owner here. The core will do it.
--
>> drivers/input/touchscreen/goodix-ts-sunrise/goodix_ts_core.c:1335:3-8: No need to set .owner here. The core will do it.
--
>> drivers/input/touchscreen/goodix-ts-sunrise/goodix_gtx5_update.c:752:2-3: Unneeded semicolon
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 parent reply other threads:[~2017-06-19 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 13:24 kbuild test robot [this message]
2017-06-19 9:29 ` Wang Yafei
2017-06-19 13:24 ` [PATCH] Input: fix semicolon.cocci warnings kbuild test robot
2017-06-19 13:24 ` [PATCH] Input: fix platform_no_drv_owner.cocci warnings kbuild test robot
2017-06-19 13:24 ` kbuild test robot
2017-06-19 15:10 ` [PATCH v2] Input: Add driver for GOODiX GTx5 series touchsereen kbuild test robot
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=201706192107.ru8ophjW%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=andrew@goodix.com \
--cc=dmitry.torokhov@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mouse@goodix.com \
--cc=rydberg@bitmath.org \
--cc=wangyafei@goodix.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
all inboxes | Powered by JetHome®