From: kernel test robot <lkp@intel.com>
To: kholk11@gmail.com, dmitry.torokhov@gmail.com
Cc: kbuild-all@lists.01.org, robh+dt@kernel.org, rydberg@bitmath.org,
priv.luk@gmail.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org,
AngeloGioacchino Del Regno <kholk11@gmail.com>
Subject: Re: [PATCH 2/3] Input: Add Novatek NT36xxx touchscreen driver
Date: Sun, 27 Sep 2020 04:23:54 +0800 [thread overview]
Message-ID: <202009270424.2k0h8UHC%lkp@intel.com> (raw)
In-Reply-To: <20200926124747.12465-3-kholk11@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2010 bytes --]
Hi,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on input/next]
[also build test WARNING on robh/for-next v5.9-rc6 next-20200925]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/kholk11-gmail-com/Add-Novatek-NT36xxx-touchscreen-driver/20200926-204916
base: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next
config: x86_64-randconfig-s032-20200927 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-201-g24bdaac6-dirty
# https://github.com/0day-ci/linux/commit/6d9ee3df7e7fa769137ec343ea91ebf87bcf24cb
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review kholk11-gmail-com/Add-Novatek-NT36xxx-touchscreen-driver/20200926-204916
git checkout 6d9ee3df7e7fa769137ec343ea91ebf87bcf24cb
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/input/touchscreen/nt36xxx.c:17:30: sparse: sparse: symbol 'nt36xxx_memory_maps' was not declared. Should it be static?
>> drivers/input/touchscreen/nt36xxx.c:25:33: sparse: sparse: symbol 'trim_id_table' was not declared. Should it be static?
>> drivers/input/touchscreen/nt36xxx.c:396:58: sparse: sparse: invalid access past the end of 'buf' (3 3)
drivers/input/touchscreen/nt36xxx.c:395:58: sparse: sparse: invalid access past the end of 'buf' (3 3)
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 33765 bytes --]
next prev parent reply other threads:[~2020-09-26 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 12:47 [PATCH 0/3] Add Novatek NT36xxx touchscreen driver kholk11
2020-09-26 12:47 ` [PATCH 1/3] dt-bindings: Add vendor prefix for Novatek Microelectronics Corp kholk11
2020-09-26 12:47 ` [PATCH 2/3] Input: Add Novatek NT36xxx touchscreen driver kholk11
2020-09-26 20:23 ` kernel test robot [this message]
2020-09-26 20:23 ` [RFC PATCH] Input: nt36xxx_memory_maps[] can be static kernel test robot
2020-09-26 12:47 ` [PATCH 3/3] dt-bindings: touchscreen: Add binding for Novatek NT36xxx series driver kholk11
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=202009270424.2k0h8UHC%lkp@intel.com \
--to=lkp@intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=kholk11@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=priv.luk@gmail.com \
--cc=robh+dt@kernel.org \
--cc=rydberg@bitmath.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