From: kernel test robot <lkp@intel.com>
To: Jason Ekstrand <jason@jlekstrand.net>
Cc: kbuild-all@lists.01.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: [Intel-gfx] [drm-intel:for-linux-next-fixes 2/2] WARNING: modpost: vmlinux.o(.text.unlikely+0x105a3b): Section mismatch in reference from the function i915_globals_exit() to the function .exit.text:__i915_globals_flush()
Date: Wed, 4 Aug 2021 06:17:32 +0800 [thread overview]
Message-ID: <202108040626.BFDOCtGS-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]
tree: git://anongit.freedesktop.org/drm-intel for-linux-next-fixes
head: 1354d830cb8f9be966cc07fc61368af27ffb7c4a
commit: 1354d830cb8f9be966cc07fc61368af27ffb7c4a [2/2] drm/i915: Call i915_globals_exit() if pci_register_device() fails
config: i386-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
git remote add drm-intel git://anongit.freedesktop.org/drm-intel
git fetch --no-tags drm-intel for-linux-next-fixes
git checkout 1354d830cb8f9be966cc07fc61368af27ffb7c4a
# save the attached .config to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>, old ones prefixed by <<):
>> WARNING: modpost: vmlinux.o(.text.unlikely+0x105a3b): Section mismatch in reference from the function i915_globals_exit() to the function .exit.text:__i915_globals_flush()
The function i915_globals_exit() references a function in an exit section.
Often the function __i915_globals_flush() has valid usage outside the exit section
and the fix is to remove the __exit annotation of __i915_globals_flush.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 65142 bytes --]
reply other threads:[~2021-08-03 22:18 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=202108040626.BFDOCtGS-lkp@intel.com \
--to=lkp@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jason@jlekstrand.net \
--cc=kbuild-all@lists.01.org \
--cc=rodrigo.vivi@intel.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