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>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Christopher Heiny <cheiny@synaptics.com>,
Stephen Chandler Paul <cpaul@redhat.com>,
Vincent Huang <vincent.huang@tw.synaptics.com>,
Jiri Kosina <jikos@kernel.org>,
Andrew Duggan <aduggan@syanptics.com>
Subject: Re: [PATCH 10/10] HID: rmi: Make hid-rmi a transport driver for synaptics-rmi4
Date: Thu, 26 Nov 2015 09:43:32 +0800 [thread overview]
Message-ID: <201511260901.oU2KNPdc%fengguang.wu@intel.com> (raw)
In-Reply-To: <1448496641-25457-1-git-send-email-aduggan@synaptics.com>
Hi Andrew,
[auto build test WARNING on input/next]
[cannot apply to v4.4-rc2 next-20151124]
url: https://github.com/0day-ci/linux/commits/Andrew-Duggan/Input-synaptics-rmi4-Synaptics-RMI4-Driver-rebased-on-4-3/20151126-081351
base: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> drivers/hid/hid-rmi.c:500:36: sparse: symbol 'rmi_hid_2d_sensor_data' was not declared. Should it be static?
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:[~2015-11-26 1:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 1:43 kbuild test robot [this message]
2015-11-26 0:10 ` Andrew Duggan
2015-11-26 1:27 ` kbuild test robot
2015-11-26 1:43 ` [RFC PATCH] HID: rmi: rmi_hid_2d_sensor_data can be static 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=201511260901.oU2KNPdc%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=aduggan@syanptics.com \
--cc=aduggan@synaptics.com \
--cc=benjamin.tissoires@redhat.com \
--cc=cheiny@synaptics.com \
--cc=cpaul@redhat.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®