public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Jiri Slaby (SUSE)" <jirislaby@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [jirislaby:devel 50/61] include/linux/console.h:36:2: error: expected identifier
Date: Sun, 17 Dec 2023 09:52:27 +0800	[thread overview]
Message-ID: <202312170941.HOLDO4AL-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux.git devel
head:   29f593717f831f4fe1c36efd2d1b0404f705bc0f
commit: 9138c2328ccc3a9bc4868c7a74b1539036a92501 [50/61] con: use enum for VESA blanking modes
config: i386-buildonly-randconfig-003-20231217 (https://download.01.org/0day-ci/archive/20231217/202312170941.HOLDO4AL-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231217/202312170941.HOLDO4AL-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/202312170941.HOLDO4AL-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from drivers/video/fbdev/gxt4500.c:13:
>> include/linux/console.h:36:2: error: expected identifier
           VESA_NO_BLANKING        = 0,
           ^
   include/uapi/linux/fb.h:297:33: note: expanded from macro 'VESA_NO_BLANKING'
   #define VESA_NO_BLANKING        0
                                   ^
   In file included from drivers/video/fbdev/gxt4500.c:13:
   include/linux/console.h:37:2: error: expected identifier
           VESA_VSYNC_SUSPEND      = 1,
           ^
   include/uapi/linux/fb.h:298:33: note: expanded from macro 'VESA_VSYNC_SUSPEND'
   #define VESA_VSYNC_SUSPEND      1
                                   ^
   In file included from drivers/video/fbdev/gxt4500.c:13:
   include/linux/console.h:38:2: error: expected identifier
           VESA_HSYNC_SUSPEND      = 2,
           ^
   include/uapi/linux/fb.h:299:33: note: expanded from macro 'VESA_HSYNC_SUSPEND'
   #define VESA_HSYNC_SUSPEND      2
                                   ^
   In file included from drivers/video/fbdev/gxt4500.c:13:
   include/linux/console.h:39:2: error: expected identifier
           VESA_POWERDOWN          = VESA_VSYNC_SUSPEND | VESA_HSYNC_SUSPEND,
           ^
   include/uapi/linux/fb.h:300:33: note: expanded from macro 'VESA_POWERDOWN'
   #define VESA_POWERDOWN          3
                                   ^
   4 errors generated.
--
   In file included from drivers/video/fbdev/matrox/g450_pll.c:17:
   In file included from drivers/video/fbdev/matrox/g450_pll.h:5:
   In file included from drivers/video/fbdev/matrox/matroxfb_base.h:37:
>> include/linux/console.h:36:2: error: expected identifier
           VESA_NO_BLANKING        = 0,
           ^
   include/uapi/linux/fb.h:297:33: note: expanded from macro 'VESA_NO_BLANKING'
   #define VESA_NO_BLANKING        0
                                   ^
   In file included from drivers/video/fbdev/matrox/g450_pll.c:17:
   In file included from drivers/video/fbdev/matrox/g450_pll.h:5:
   In file included from drivers/video/fbdev/matrox/matroxfb_base.h:37:
   include/linux/console.h:37:2: error: expected identifier
           VESA_VSYNC_SUSPEND      = 1,
           ^
   include/uapi/linux/fb.h:298:33: note: expanded from macro 'VESA_VSYNC_SUSPEND'
   #define VESA_VSYNC_SUSPEND      1
                                   ^
   In file included from drivers/video/fbdev/matrox/g450_pll.c:17:
   In file included from drivers/video/fbdev/matrox/g450_pll.h:5:
   In file included from drivers/video/fbdev/matrox/matroxfb_base.h:37:
   include/linux/console.h:38:2: error: expected identifier
           VESA_HSYNC_SUSPEND      = 2,
           ^
   include/uapi/linux/fb.h:299:33: note: expanded from macro 'VESA_HSYNC_SUSPEND'
   #define VESA_HSYNC_SUSPEND      2
                                   ^
   In file included from drivers/video/fbdev/matrox/g450_pll.c:17:
   In file included from drivers/video/fbdev/matrox/g450_pll.h:5:
   In file included from drivers/video/fbdev/matrox/matroxfb_base.h:37:
   include/linux/console.h:39:2: error: expected identifier
           VESA_POWERDOWN          = VESA_VSYNC_SUSPEND | VESA_HSYNC_SUSPEND,
           ^
   include/uapi/linux/fb.h:300:33: note: expanded from macro 'VESA_POWERDOWN'
   #define VESA_POWERDOWN          3
                                   ^
   drivers/video/fbdev/matrox/g450_pll.c:410:18: warning: variable 'mnp' set but not used [-Wunused-but-set-variable]
                                   unsigned int mnp;
                                                ^
   1 warning and 4 errors generated.


vim +36 include/linux/console.h

    33	
    34	/* Note: fbcon defines the below as macros for userspace (in fb.h). */
    35	enum vesa_blank_mode {
  > 36		VESA_NO_BLANKING	= 0,
    37		VESA_VSYNC_SUSPEND	= 1,
    38		VESA_HSYNC_SUSPEND	= 2,
    39		VESA_POWERDOWN		= VESA_VSYNC_SUSPEND | VESA_HSYNC_SUSPEND,
    40		VESA_BLANK_MAX		= VESA_POWERDOWN,
    41	};
    42	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2023-12-17  1:53 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=202312170941.HOLDO4AL-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jirislaby@kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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