From: kbuild test robot <lkp@intel.com>
To: Andrew Duggan <aduggan@synaptics.com>
Cc: kbuild-all@01.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org,
Andrew Duggan <aduggan@synaptics.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Christopher Heiny <cheiny@synaptics.com>,
Stephen Chandler Paul <cpaul@redhat.com>,
Vincent Huang <vincent.huang@tw.synaptics.com>,
Chris Healy <cphealy@gmail.com>,
Andrey Gusakov <andrey.gusakov@cogentembedded.com>
Subject: Re: [PATCH v4 01/10] Input: synaptics-rmi4: Add support for Synaptics RMI4 devices
Date: Wed, 10 Feb 2016 10:27:44 +0800 [thread overview]
Message-ID: <201602101040.KxxuxnZe%fengguang.wu@intel.com> (raw)
In-Reply-To: <1455068422-11916-1-git-send-email-aduggan@synaptics.com>
Hi Andrew,
[auto build test WARNING on input/next]
[also build test WARNING on v4.5-rc3 next-20160209]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Andrew-Duggan/Input-synaptics-rmi4-Synaptics-RMI4-Driver/20160210-094628
base: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next
coccinelle warnings: (new ones prefixed by >>)
>> drivers/input/rmi4/rmi_bus.c:295:20-21: WARNING: Use ARRAY_SIZE
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:[~2016-02-10 2:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 2:27 kbuild test robot [this message]
2016-02-10 1:40 ` Andrew Duggan
2016-02-10 2:27 ` [PATCH] Input: synaptics-rmi4: fix array_size.cocci warnings 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=201602101040.KxxuxnZe%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=aduggan@synaptics.com \
--cc=andrey.gusakov@cogentembedded.com \
--cc=benjamin.tissoires@redhat.com \
--cc=cheiny@synaptics.com \
--cc=cpaul@redhat.com \
--cc=cphealy@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jikos@kernel.org \
--cc=kbuild-all@01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vincent.huang@tw.synaptics.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®