From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH] fbdev: mb862xxfb: Silence possibly unused functions
Date: Mon, 24 Aug 2026 07:59:48 +0800 [thread overview]
Message-ID: <202608240747.dZkqSMpL-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "linux-review patch is more than 7 days old, verify it wasn't already superseded"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20260808083648.257464-1-deller@gmx.de>
References: <20260808083648.257464-1-deller@gmx.de>
TO: Helge Deller <deller@gmx.de>
TO: linux-fbdev@vger.kernel.org
TO: dri-devel@lists.freedesktop.org
Hi Helge,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on drm-tip/drm-tip v7.2]
[cannot apply to linus/master next-20260821]
[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/Helge-Deller/fbdev-mb862xxfb-Silence-possibly-unused-functions/20260808-103648
base: https://gitlab.freedesktop.org/drm/misc/kernel.git drm-misc-next
patch link: https://lore.kernel.org/r/20260808083648.257464-1-deller%40gmx.de
patch subject: [PATCH] fbdev: mb862xxfb: Silence possibly unused functions
:::::: branch date: 30 hours ago
:::::: commit date: 30 hours ago
config: parisc-allyesconfig (https://download.01.org/0day-ci/archive/20260824/202608240747.dZkqSMpL-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260824/202608240747.dZkqSMpL-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/r/202608240747.dZkqSMpL-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/compiler_types.h:88,
from <command-line>:
>> include/linux/compiler_attributes.h:352:41: error: expected ',' or ';' before '__attribute__'
352 | #define __maybe_unused __attribute__((__unused__))
| ^~~~~~~~~~~~~
drivers/video/fbdev/mb862xx/mb862xxfbdrv.c:571:33: note: in expansion of macro '__maybe_unused'
571 | static DEVICE_ATTR_RO(dispregs) __maybe_unused;
| ^~~~~~~~~~~~~~
vim +352 include/linux/compiler_attributes.h
fd7eea27a3aed7 Heiko Carstens 2024-02-05 343
a3f8a30f3f0079 Miguel Ojeda 2018-08-30 344 /*
a3f8a30f3f0079 Miguel Ojeda 2018-08-30 345 * gcc: https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-unused-function-attribute
a3f8a30f3f0079 Miguel Ojeda 2018-08-30 346 * gcc: https://gcc.gnu.org/onlinedocs/gcc/Common-Type-Attributes.html#index-unused-type-attribute
a3f8a30f3f0079 Miguel Ojeda 2018-08-30 347 * gcc: https://gcc.gnu.org/onlinedocs/gcc/Common-Variable-Attributes.html#index-unused-variable-attribute
a3f8a30f3f0079 Miguel Ojeda 2018-08-30 348 * gcc: https://gcc.gnu.org/onlinedocs/gcc/Label-Attributes.html#index-unused-label-attribute
a3f8a30f3f0079 Miguel Ojeda 2018-08-30 349 * clang: https://clang.llvm.org/docs/AttributeReference.html#maybe-unused-unused
a3f8a30f3f0079 Miguel Ojeda 2018-08-30 350 */
a3f8a30f3f0079 Miguel Ojeda 2018-08-30 351 #define __always_unused __attribute__((__unused__))
a3f8a30f3f0079 Miguel Ojeda 2018-08-30 @352 #define __maybe_unused __attribute__((__unused__))
a3f8a30f3f0079 Miguel Ojeda 2018-08-30 353
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-08-24 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 23:59 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-08 8:36 [PATCH] fbdev: mb862xxfb: Silence possibly unused functions Helge Deller
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=202608240747.dZkqSMpL-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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 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.