From: kbuild test robot <lkp@intel.com>
To: Tony Lindgren <tony@atomide.com>
Cc: kbuild-all@lists.01.org, linux-omap@vger.kernel.org
Subject: [omap:droid4-pending-v5.7 4/27] drivers/input/keyboard/omap4-keypad.c:215:7: warning: variable 'events' set but not used
Date: Sat, 23 May 2020 05:01:45 +0800 [thread overview]
Message-ID: <202005230542.MHgpwpYQ%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2199 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git droid4-pending-v5.7
head: c79f709cdba38b9a054d444f4eabc0e1126f06cc
commit: c5fb8fb9beac4d489c2f54f6122b6ae11d1e5611 [4/27] Input: omap4-keypad - check state again for lost key-up interrupts
config: alpha-randconfig-r033-20200522 (attached as .config)
compiler: alpha-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout c5fb8fb9beac4d489c2f54f6122b6ae11d1e5611
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=alpha
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>, old ones prefixed by <<):
drivers/input/keyboard/omap4-keypad.c: In function 'omap4_keypad_scan_keys':
drivers/input/keyboard/omap4-keypad.c:162:6: warning: variable 'keys_up' set but not used [-Wunused-but-set-variable]
162 | int keys_up, keys_down;
| ^~~~~~~
drivers/input/keyboard/omap4-keypad.c: In function 'omap4_keypad_work':
>> drivers/input/keyboard/omap4-keypad.c:215:7: warning: variable 'events' set but not used [-Wunused-but-set-variable]
215 | bool events;
| ^~~~~~
vim +/events +215 drivers/input/keyboard/omap4-keypad.c
206
207 /*
208 * Errata ID i689 "1.32 Keyboard Key Up Event Can Be Missed".
209 * Interrupt may not happen for key-up events.
210 */
211 static void omap4_keypad_work(struct work_struct *work)
212 {
213 struct omap4_keypad *keypad_data =
214 container_of(work, struct omap4_keypad, key_work.work);
> 215 bool events;
216 u32 active;
217
218 active = kbd_readl(keypad_data, OMAP4_KBD_STATEMACHINE);
219 if (active)
220 return;
221
222 dev_dbg(keypad_data->input->dev.parent, "idle with events\n");
223 events = omap4_keypad_scan_keys(keypad_data, true);
224 }
225
---
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: 35556 bytes --]
reply other threads:[~2020-05-22 21:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202005230542.MHgpwpYQ%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).