From: kbuild test robot <lkp@intel.com>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: kbuild-all@01.org, Wolfram Sang <wsa@the-dreams.de>,
Jean Delvare <jdelvare@suse.de>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Andrew Duggan <aduggan@synaptics.com>,
Christopher Heiny <cheiny@synaptics.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 2/2] Input: synaptics-rmi4 - add SMBus support
Date: Sat, 25 Jun 2016 05:47:31 +0800 [thread overview]
Message-ID: <201606250504.23UjMfXF%fengguang.wu@intel.com> (raw)
In-Reply-To: <1466779303-8658-1-git-send-email-benjamin.tissoires@redhat.com>
Hi,
[auto build test WARNING on wsa/i2c/for-next]
[also build test WARNING on v4.7-rc4 next-20160624]
[cannot apply to input/next]
[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/Benjamin-Tissoires/i2c-i801-add-support-of-Host-Notify/20160624-224821
base: https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux i2c/for-next
coccinelle warnings: (new ones prefixed by >>)
>> drivers/input/rmi4/rmi_smbus.c:448: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 prev parent reply other threads:[~2016-06-24 21:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 14:39 [PATCH v9 1/2] i2c: i801: add support of Host Notify Benjamin Tissoires
2016-06-24 14:41 ` [PATCH v9 2/2] Input: synaptics-rmi4 - add SMBus support Benjamin Tissoires
2016-06-24 21:47 ` [PATCH] Input: fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-06-24 21:47 ` kbuild test robot [this message]
2016-07-05 15:40 ` [PATCH v9 1/2] i2c: i801: add support of Host Notify Wolfram Sang
2016-07-18 14:12 ` Jean Delvare
2016-07-28 9:44 ` Benjamin Tissoires
2016-08-01 13:33 ` Jean Delvare
2016-08-19 13:19 ` Benjamin Tissoires
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=201606250504.23UjMfXF%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=aduggan@synaptics.com \
--cc=benjamin.tissoires@redhat.com \
--cc=cheiny@synaptics.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jdelvare@suse.de \
--cc=kbuild-all@01.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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).