From: kernel test robot <lkp@intel.com>
To: "Yury V. Zaytsev" <yury@shurup.com>,
gregkh@linuxfoundation.org, jirislaby@kernel.org,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, "Yury V. Zaytsev" <yury@shurup.com>
Subject: Re: [PATCH RESEND] tty: vt: make defkeymap for shifted F-keys consistent with kbd
Date: Thu, 6 Mar 2025 15:20:39 +0800 [thread overview]
Message-ID: <202503061554.ZQPrGM8H-lkp@intel.com> (raw)
In-Reply-To: <20250301132108.62761-1-yury@shurup.com>
Hi Yury,
kernel test robot noticed the following build warnings:
[auto build test WARNING on tty/tty-testing]
[also build test WARNING on linus/master v6.14-rc5 next-20250305]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Yury-V-Zaytsev/tty-vt-make-defkeymap-for-shifted-F-keys-consistent-with-kbd/20250301-214942
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
patch link: https://lore.kernel.org/r/20250301132108.62761-1-yury%40shurup.com
patch subject: [PATCH RESEND] tty: vt: make defkeymap for shifted F-keys consistent with kbd
config: csky-randconfig-r111-20250305 (https://download.01.org/0day-ci/archive/20250306/202503061554.ZQPrGM8H-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 14.2.0
reproduce: (https://download.01.org/0day-ci/archive/20250306/202503061554.ZQPrGM8H-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202503061554.ZQPrGM8H-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/tty/vt/defkeymap.c:254:42: sparse: sparse: Using plain integer as NULL pointer
drivers/tty/vt/defkeymap.c:255:35: sparse: sparse: Using plain integer as NULL pointer
drivers/tty/vt/defkeymap.c:255:38: sparse: sparse: Using plain integer as NULL pointer
drivers/tty/vt/defkeymap.c:256:18: sparse: sparse: Using plain integer as NULL pointer
drivers/tty/vt/defkeymap.c:256:21: sparse: sparse: Using plain integer as NULL pointer
drivers/tty/vt/defkeymap.c:256:24: sparse: sparse: Using plain integer as NULL pointer
drivers/tty/vt/defkeymap.c:257:25: sparse: sparse: Using plain integer as NULL pointer
drivers/tty/vt/defkeymap.c:260:14: sparse: sparse: symbol 'keymap_count' was not declared. Should it be static?
drivers/tty/vt/defkeymap.c:268:6: sparse: sparse: symbol 'func_buf' was not declared. Should it be static?
drivers/tty/vt/defkeymap.c:303:6: sparse: sparse: symbol 'funcbufptr' was not declared. Should it be static?
drivers/tty/vt/defkeymap.c:304:5: sparse: sparse: symbol 'funcbufsize' was not declared. Should it be static?
drivers/tty/vt/defkeymap.c:305:5: sparse: sparse: symbol 'funcbufleft' was not declared. Should it be static?
drivers/tty/vt/defkeymap.c:335:9: sparse: sparse: Using plain integer as NULL pointer
drivers/tty/vt/defkeymap.c:336:9: sparse: sparse: Using plain integer as NULL pointer
drivers/tty/vt/defkeymap.c:342:9: sparse: sparse: Using plain integer as NULL pointer
drivers/tty/vt/defkeymap.c:307:6: sparse: sparse: symbol 'func_table' was not declared. Should it be static?
drivers/tty/vt/defkeymap.c:345:18: sparse: sparse: symbol 'accent_table' was not declared. Should it be static?
drivers/tty/vt/defkeymap.c:382:14: sparse: sparse: symbol 'accent_table_size' was not declared. Should it be static?
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-03-06 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-19 18:47 [PATCH] tty: vt: make defkeymap for shifted F-keys consistent with kbd Yury V. Zaytsev
2025-03-01 13:21 ` [PATCH RESEND] " Yury V. Zaytsev
2025-03-06 7:20 ` kernel test robot [this message]
2025-03-17 13:37 ` Yury V. Zaytsev
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=202503061554.ZQPrGM8H-lkp@intel.com \
--to=lkp@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yury@shurup.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