From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [linux-next:master 2417/10784] drivers/video/console/newport_con.c:362:15: error: 'struct vc_data' has no member named 'vc_color'; did you mean
Date: Fri, 24 Jul 2020 13:57:36 +0800 [thread overview]
Message-ID: <202007241318.wXYkumEO%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5006 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 4f5baedd579d5499876eadb1de12ddfdadcaa3ab
commit: 28bc24fc46f9c9f39ddefb424d6072041805b563 [2417/10784] vc: separate state
config: mips-randconfig-r004-20200724 (attached as .config)
compiler: mips-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 28bc24fc46f9c9f39ddefb424d6072041805b563
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=mips
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/video/console/newport_con.c: In function 'newport_show_logo':
drivers/video/console/newport_con.c:132:1: warning: no return statement in function returning non-void [-Wreturn-type]
132 | }
| ^
drivers/video/console/newport_con.c: In function 'newport_clear':
>> drivers/video/console/newport_con.c:362:15: error: 'struct vc_data' has no member named 'vc_color'; did you mean 'vc_cols'?
362 | (vc->vc_color & 0xf0) >> 4);
| ^~~~~~~~
| vc_cols
drivers/video/console/newport_con.c:365:15: error: 'struct vc_data' has no member named 'vc_color'; did you mean 'vc_cols'?
365 | (vc->vc_color & 0xf0) >> 4);
| ^~~~~~~~
| vc_cols
drivers/video/console/newport_con.c:367:15: error: 'struct vc_data' has no member named 'vc_color'; did you mean 'vc_cols'?
367 | (vc->vc_color & 0xf0) >> 4);
| ^~~~~~~~
| vc_cols
drivers/video/console/newport_con.c: In function 'newport_scroll':
drivers/video/console/newport_con.c:591:15: error: 'struct vc_data' has no member named 'vc_color'; did you mean 'vc_cols'?
591 | (vc->vc_color & 0xf0) >> 4);
| ^~~~~~~~
| vc_cols
drivers/video/console/newport_con.c:595:15: error: 'struct vc_data' has no member named 'vc_color'; did you mean 'vc_cols'?
595 | (vc->vc_color & 0xf0) >> 4);
| ^~~~~~~~
| vc_cols
drivers/video/console/newport_con.c: At top level:
drivers/video/console/newport_con.c:745:12: warning: no previous prototype for 'newport_console_init' [-Wmissing-prototypes]
745 | int __init newport_console_init(void)
| ^~~~~~~~~~~~~~~~~~~~
drivers/video/console/newport_con.c:750:13: warning: no previous prototype for 'newport_console_exit' [-Wmissing-prototypes]
750 | void __exit newport_console_exit(void)
| ^~~~~~~~~~~~~~~~~~~~
vim +362 drivers/video/console/newport_con.c
^1da177e4c3f415 Linus Torvalds 2005-04-16 349
^1da177e4c3f415 Linus Torvalds 2005-04-16 350 static void newport_clear(struct vc_data *vc, int sy, int sx, int height,
^1da177e4c3f415 Linus Torvalds 2005-04-16 351 int width)
^1da177e4c3f415 Linus Torvalds 2005-04-16 352 {
^1da177e4c3f415 Linus Torvalds 2005-04-16 353 int xend = ((sx + width) << 3) - 1;
^1da177e4c3f415 Linus Torvalds 2005-04-16 354 int ystart = ((sy << 4) + topscan) & 0x3ff;
^1da177e4c3f415 Linus Torvalds 2005-04-16 355 int yend = (((sy + height) << 4) + topscan - 1) & 0x3ff;
^1da177e4c3f415 Linus Torvalds 2005-04-16 356
^1da177e4c3f415 Linus Torvalds 2005-04-16 357 if (logo_active)
^1da177e4c3f415 Linus Torvalds 2005-04-16 358 return;
^1da177e4c3f415 Linus Torvalds 2005-04-16 359
^1da177e4c3f415 Linus Torvalds 2005-04-16 360 if (ystart < yend) {
^1da177e4c3f415 Linus Torvalds 2005-04-16 361 newport_clear_screen(sx << 3, ystart, xend, yend,
^1da177e4c3f415 Linus Torvalds 2005-04-16 @362 (vc->vc_color & 0xf0) >> 4);
^1da177e4c3f415 Linus Torvalds 2005-04-16 363 } else {
^1da177e4c3f415 Linus Torvalds 2005-04-16 364 newport_clear_screen(sx << 3, ystart, xend, 1023,
^1da177e4c3f415 Linus Torvalds 2005-04-16 365 (vc->vc_color & 0xf0) >> 4);
^1da177e4c3f415 Linus Torvalds 2005-04-16 366 newport_clear_screen(sx << 3, 0, xend, yend,
^1da177e4c3f415 Linus Torvalds 2005-04-16 367 (vc->vc_color & 0xf0) >> 4);
^1da177e4c3f415 Linus Torvalds 2005-04-16 368 }
^1da177e4c3f415 Linus Torvalds 2005-04-16 369 }
^1da177e4c3f415 Linus Torvalds 2005-04-16 370
:::::: The code at line 362 was first introduced by commit
:::::: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Linux-2.6.12-rc2
:::::: TO: Linus Torvalds <torvalds@ppc970.osdl.org>
:::::: CC: Linus Torvalds <torvalds@ppc970.osdl.org>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 21416 bytes --]
next reply other threads:[~2020-07-24 5:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 5:57 kernel test robot [this message]
2020-07-24 6:27 ` [PATCH] newport_con: vc_color is now in state Jiri Slaby
2020-07-24 6:27 ` Jiri Slaby
2020-07-24 6:27 ` Jiri Slaby
2020-07-24 7:58 ` Greg KH
2020-07-24 7:58 ` Greg KH
2020-07-24 7:58 ` Greg KH
2020-07-24 7:59 ` Jiri Slaby
2020-07-24 7:59 ` Jiri Slaby
2020-07-24 7:59 ` Jiri Slaby
2020-07-24 9:30 ` Sergei Shtylyov
2020-07-24 9:30 ` Sergei Shtylyov
2020-07-24 9:30 ` Sergei Shtylyov
2020-07-24 9:38 ` Greg KH
2020-07-24 9:38 ` Greg KH
2020-07-24 9:38 ` Greg KH
2020-07-24 10:30 ` Jiri Slaby
2020-07-24 10:30 ` Jiri Slaby
2020-07-24 10:30 ` Jiri Slaby
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=202007241318.wXYkumEO%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.