From: Pavel Machek <pavel@ucw.cz>
To: kernel test robot <lkp@intel.com>
Cc: "Gustavo A. R. Silva" <gustavoars@kernel.org>,
kbuild-all@lists.01.org, linux-leds@vger.kernel.org
Subject: Re: [pavel-linux-leds:for-next 17/17] WARNING: modpost: vmlinux.o(.text+0x2492): Section mismatch in reference from the function ret_from_kernel_thread() to the variable .init.text:.L904
Date: Mon, 13 Jul 2020 08:44:52 +0200 [thread overview]
Message-ID: <20200713064452.GA30654@amd> (raw)
In-Reply-To: <202007131331.ta5KKp3K%lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1648 bytes --]
Hi!
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git for-next
> head: cf1a1a6a7d81d73bcb5568b23572d6fd593add87
> commit: cf1a1a6a7d81d73bcb5568b23572d6fd593add87 [17/17] leds: gpio: Use struct_size() in devm_kzalloc()
> config: riscv-randconfig-r012-20200712 (attached as .config)
> compiler: riscv32-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 cf1a1a6a7d81d73bcb5568b23572d6fd593add87
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv
>
> 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 >>):
These look weird.
> >> WARNING: modpost: vmlinux.o(.text+0xd475de): Section mismatch in reference from the function radeon_audio_init() to the variable .init.text:.LBE12095
> The function radeon_audio_init() references
> the variable __init .LBE12095.
> This is often because radeon_audio_init lacks a __init
> annotation or the annotation of .LBE12095 is wrong.
> --
And in the code we are not touching.
Is the report about just 17/17, or could it be other patch in the
series?
Is it possible that something simply went wrong with testing?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: kbuild-all@lists.01.org
Subject: Re: [pavel-linux-leds:for-next 17/17] WARNING: modpost: vmlinux.o(.text+0x2492): Section mismatch in reference from the function ret_from_kernel_thread() to the variable .init.text:.L904
Date: Mon, 13 Jul 2020 08:44:52 +0200 [thread overview]
Message-ID: <20200713064452.GA30654@amd> (raw)
In-Reply-To: <202007131331.ta5KKp3K%lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1648 bytes --]
Hi!
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git for-next
> head: cf1a1a6a7d81d73bcb5568b23572d6fd593add87
> commit: cf1a1a6a7d81d73bcb5568b23572d6fd593add87 [17/17] leds: gpio: Use struct_size() in devm_kzalloc()
> config: riscv-randconfig-r012-20200712 (attached as .config)
> compiler: riscv32-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 cf1a1a6a7d81d73bcb5568b23572d6fd593add87
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv
>
> 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 >>):
These look weird.
> >> WARNING: modpost: vmlinux.o(.text+0xd475de): Section mismatch in reference from the function radeon_audio_init() to the variable .init.text:.LBE12095
> The function radeon_audio_init() references
> the variable __init .LBE12095.
> This is often because radeon_audio_init lacks a __init
> annotation or the annotation of .LBE12095 is wrong.
> --
And in the code we are not touching.
Is the report about just 17/17, or could it be other patch in the
series?
Is it possible that something simply went wrong with testing?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2020-07-13 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 5:29 [pavel-linux-leds:for-next 17/17] WARNING: modpost: vmlinux.o(.text+0x2492): Section mismatch in reference from the function ret_from_kernel_thread() to the variable .init.text:.L904 kernel test robot
2020-07-13 5:29 ` kernel test robot
2020-07-13 6:44 ` Pavel Machek [this message]
2020-07-13 6:44 ` Pavel Machek
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=20200713064452.GA30654@amd \
--to=pavel@ucw.cz \
--cc=gustavoars@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-leds@vger.kernel.org \
--cc=lkp@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 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.