From: kbuild test robot <lkp@intel.com>
To: Anthony Kim <anthony.kim@hideep.com>
Cc: kbuild-all@01.org, dmitry.torokhov@gmail.com, robh+dt@kernel.org,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Anthony Kim <anthony.kim@hideep.com>
Subject: Re: [PATCH] Input: add support for HiDeep touchscreen
Date: Wed, 13 Sep 2017 16:51:06 +0800 [thread overview]
Message-ID: <201709131645.1eY8eUTb%fengguang.wu@intel.com> (raw)
In-Reply-To: <1505114862-32489-1-git-send-email-anthony.kim@hideep.com>
[-- Attachment #1: Type: text/plain, Size: 2977 bytes --]
Hi Anthony,
[auto build test WARNING on input/next]
[also build test WARNING on v4.13 next-20170912]
[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/Anthony-Kim/Input-add-support-for-HiDeep-touchscreen/20170913-140147
base: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next
config: m68k-allmodconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 4.9.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=m68k
All warnings (new ones prefixed by >>):
drivers/input/touchscreen/hideep.c: In function 'hideep_update_firmware':
>> drivers/input/touchscreen/hideep.c:576:4: warning: format '%ld' expects argument of type 'long int', but argument 3 has type 'size_t' [-Wformat=]
fw_entry->size, ts->fw_size);
^
vim +576 drivers/input/touchscreen/hideep.c
558
559 static int hideep_update_firmware(struct hideep_ts *ts, const char *fn)
560 {
561 int ret;
562 int retry, retry_cnt = 3;
563 const struct firmware *fw_entry;
564
565 dev_dbg(&ts->client->dev, "enter");
566 ret = request_firmware(&fw_entry, fn, &ts->client->dev);
567
568 if (ret != 0) {
569 dev_err(&ts->client->dev, "request_firmware : fail(%d)", ret);
570 return ret;
571 }
572
573 if (fw_entry->size > ts->fw_size) {
574 dev_err(&ts->client->dev,
575 "file size(%ld) is big more than fw memory size(%d)",
> 576 fw_entry->size, ts->fw_size);
577 release_firmware(fw_entry);
578 return -EFBIG;
579 }
580
581 /* chip specific code for flash fuse */
582 mutex_lock(&ts->dev_mutex);
583
584 ts->dev_state = state_updating;
585
586 /* enter program mode */
587 ret = hideep_enter_pgm(ts);
588
589 if (ret)
590 return ret;
591
592 /* comparing & programming each page, if the memory of specified
593 * page is exactly same, no need to update.
594 */
595 for (retry = 0; retry < retry_cnt; retry++) {
596 hideep_program_nvm(ts, fw_entry->data, fw_entry->size);
597
598 ret = hideep_verify_nvm(ts, fw_entry->data, fw_entry->size);
599 if (!ret)
600 break;
601 }
602
603 if (retry < retry_cnt)
604 dev_dbg(&ts->client->dev, "update success!!!");
605 else
606 dev_err(&ts->client->dev, "update failed!!!");
607
608 SW_RESET_IN_PGM(1000);
609
610 ts->dev_state = state_normal;
611
612 mutex_unlock(&ts->dev_mutex);
613
614 release_firmware(fw_entry);
615
616 return ret;
617 }
618
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 40413 bytes --]
next prev parent reply other threads:[~2017-09-13 8:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1500965607-2446-1-git-send-email-anthony.kim@hideep.com>
2017-08-22 9:03 ` Anthony Kim
2017-08-23 0:07 ` Rob Herring
2017-08-31 6:51 ` Dmitry Torokhov
2017-09-11 7:27 ` Anthony Kim
2017-09-12 14:17 ` Rob Herring
2017-09-13 7:50 ` kbuild test robot
2017-09-13 8:51 ` kbuild test robot [this message]
2017-09-14 4:36 ` Anthony Kim
2017-09-14 18:51 ` Dmitry Torokhov
2017-09-18 19:03 ` Rob Herring
2017-09-26 1:42 ` Anthony Kim
2017-09-26 3:28 ` Anthony Kim
2017-09-26 3:30 ` Anthony Kim
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=201709131645.1eY8eUTb%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=anthony.kim@hideep.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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®