From: kbuild test robot <lkp@intel.com>
To: Johnny Chuang <johnny.chuang@emc.com.tw>
Cc: kbuild-all@01.org, Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Daniel Kurtz <djkurtz@gmail.com>,
Jennifer Tsai <jennifer.tsai@emc.com.tw>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
James Chen <james.chen@emc.com.tw>,
Paul Liang <paul.liang@emc.com.tw>,
Jeff Chuang <jeff.chuang@emc.com.tw>,
Johnny Chuang <johnny.chuang@emc.com.tw>
Subject: Re: [PATCH] Input: elants_i2c - get product id on recovery mode for FW update
Date: Thu, 25 Aug 2016 16:31:08 +0800 [thread overview]
Message-ID: <201608251612.s8EzF0c8%fengguang.wu@intel.com> (raw)
In-Reply-To: <1472028265-5018-1-git-send-email-johnny.chuang@emc.com.tw>
[-- Attachment #1: Type: text/plain, Size: 1745 bytes --]
Hi Johnny,
[auto build test ERROR on input/next]
[also build test ERROR on v4.8-rc3 next-20160824]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]
url: https://github.com/0day-ci/linux/commits/Johnny-Chuang/Input-elants_i2c-get-product-id-on-recovery-mode-for-FW-update/20160824-170047
base: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next
config: i386-allmodconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
drivers/input/touchscreen/elants_i2c.c: In function 'elants_i2c_query_hw_version':
>> drivers/input/touchscreen/elants_i2c.c:322:12: error: 'clent' undeclared (first use in this function)
dev_err(&clent->dev,
^~~~~
drivers/input/touchscreen/elants_i2c.c:322:12: note: each undeclared identifier is reported only once for each function it appears in
vim +/clent +322 drivers/input/touchscreen/elants_i2c.c
316
317 dev_dbg(&client->dev, "read fw id error=%d, buf=%*phC\n",
318 error, (int)sizeof(resp), resp);
319 }
320
321 if (error) {
> 322 dev_err(&clent->dev,
323 "Failed to read fw id: %d\n", error);
324 return error;
325 }
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 54574 bytes --]
next prev parent reply other threads:[~2016-08-25 8:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 8:44 Johnny Chuang
2016-08-25 8:31 ` kbuild test robot [this message]
2016-08-25 10:11 ` Johnny Chuang
2016-08-25 16:40 ` Dmitry Torokhov
2016-09-23 8:01 ` [PATCH v3] " Johnny Chuang
2016-09-23 21:30 ` Dmitry Torokhov
2016-09-26 2:30 ` Johnny.Chuang
2016-09-27 2:54 ` '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=201608251612.s8EzF0c8%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=djkurtz@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=james.chen@emc.com.tw \
--cc=jeff.chuang@emc.com.tw \
--cc=jennifer.tsai@emc.com.tw \
--cc=johnny.chuang@emc.com.tw \
--cc=kbuild-all@01.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.liang@emc.com.tw \
/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®