From: kernel test robot <lkp@intel.com>
To: oushixiong1025@163.com, Helge Deller <deller@gmx.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Peter Jones <pjones@redhat.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, Shixiong Ou <oushixiong@kylinos.cn>
Subject: Re: [PATCH] fbdev: efifb: do not load efifb if PCI BAR has changed but not fixuped
Date: Fri, 27 Jun 2025 05:27:55 +0800 [thread overview]
Message-ID: <202506270558.awnEnyeN-lkp@intel.com> (raw)
In-Reply-To: <20250626094937.515552-1-oushixiong1025@163.com>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.16-rc3 next-20250626]
[cannot apply to drm-misc/drm-misc-next]
[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/oushixiong1025-163-com/fbdev-efifb-do-not-load-efifb-if-PCI-BAR-has-changed-but-not-fixuped/20250626-175111
base: linus/master
patch link: https://lore.kernel.org/r/20250626094937.515552-1-oushixiong1025%40163.com
patch subject: [PATCH] fbdev: efifb: do not load efifb if PCI BAR has changed but not fixuped
config: arm-allnoconfig (https://download.01.org/0day-ci/archive/20250627/202506270558.awnEnyeN-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project e04c938cc08a90ae60440ce22d072ebc69d67ee8)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250627/202506270558.awnEnyeN-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/202506270558.awnEnyeN-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from init/main.c:110:
In file included from arch/arm/include/asm/setup.h:14:
>> include/linux/screen_info.h:145:6: warning: no previous prototype for function 'screen_info_is_useful' [-Wmissing-prototypes]
145 | bool screen_info_is_useful(void)
| ^
include/linux/screen_info.h:145:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
145 | bool screen_info_is_useful(void)
| ^
| static
1 warning generated.
vim +/screen_info_is_useful +145 include/linux/screen_info.h
139
140 #if defined(CONFIG_PCI)
141 bool screen_info_is_useful(void);
142 void screen_info_apply_fixups(void);
143 struct pci_dev *screen_info_pci_dev(const struct screen_info *si);
144 #else
> 145 bool screen_info_is_useful(void)
146 {
147 return true;
148 }
149 static inline void screen_info_apply_fixups(void)
150 { }
151 static inline struct pci_dev *screen_info_pci_dev(const struct screen_info *si)
152 {
153 return NULL;
154 }
155 #endif
156
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-06-26 21:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 9:49 oushixiong1025
2025-06-26 10:31 ` Thomas Zimmermann
2025-06-27 8:07 ` Shixiong Ou
2025-06-27 8:12 ` Thomas Zimmermann
[not found] ` <bbfebeac-a5b4-4350-a4e8-3da8a5f0efad@163.com>
2025-06-27 9:04 ` Thomas Zimmermann
2025-06-26 21:17 ` kernel test robot
2025-06-26 21:27 ` kernel test robot [this message]
2025-06-27 9:10 ` Thomas Zimmermann
2025-06-27 9:13 ` Thomas Zimmermann
2025-07-07 9:24 ` Shixiong Ou
2025-07-07 9:28 ` Thomas Zimmermann
2025-07-07 10:02 ` Shixiong Ou
2025-07-07 10:17 ` Thomas Zimmermann
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=202506270558.awnEnyeN-lkp@intel.com \
--to=lkp@intel.com \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oushixiong1025@163.com \
--cc=oushixiong@kylinos.cn \
--cc=pjones@redhat.com \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®