more warnings

3 messages, 2 authors, 2018-03-15 · open the first message on its own page

more warnings

From: Stephen Rothwell <hidden>
Date: 2018-03-14 05:23:52

Hi all,

I also get these from a powerpc allyesconfig build of linux-next:

WARNING: vmlinux.o(.text+0x7c81c): Section mismatch in reference from the function .stop_machine_change_mapping() to the function .meminit.text:.create_physical_mapping()
The function .stop_machine_change_mapping() references
the function __meminit .create_physical_mapping().
This is often because .stop_machine_change_mapping lacks a __meminit 
annotation or the annotation of .create_physical_mapping is wrong.

WARNING: vmlinux.o(.text+0x7c828): Section mismatch in reference from the function .stop_machine_change_mapping() to the function .meminit.text:.create_physical_mapping()
The function .stop_machine_change_mapping() references
the function __meminit .create_physical_mapping().
This is often because .stop_machine_change_mapping lacks a __meminit 
annotation or the annotation of .create_physical_mapping is wrong.

-- 
Cheers,
Stephen Rothwell

Re: more warnings

From: Balbir Singh <bsingharora@gmail.com>
Date: 2018-03-15 08:42:36

On Wed, Mar 14, 2018 at 4:23 PM, Stephen Rothwell [off-list ref] wrote:
Hi all,

I also get these from a powerpc allyesconfig build of linux-next:

WARNING: vmlinux.o(.text+0x7c81c): Section mismatch in reference from the function .stop_machine_change_mapping() to the function .meminit.text:.create_physical_mapping()
The function .stop_machine_change_mapping() references
the function __meminit .create_physical_mapping().
This is often because .stop_machine_change_mapping lacks a __meminit
annotation or the annotation of .create_physical_mapping is wrong.

WARNING: vmlinux.o(.text+0x7c828): Section mismatch in reference from the function .stop_machine_change_mapping() to the function .meminit.text:.create_physical_mapping()
The function .stop_machine_change_mapping() references
the function __meminit .create_physical_mapping().
This is often because .stop_machine_change_mapping lacks a __meminit
annotation or the annotation of .create_physical_mapping is wrong.

Hi, Stephen

Patches have been sent to fix this - http://patchwork.ozlabs.org/patch/883991/

Balbir Singh

Re: more warnings

From: Stephen Rothwell <hidden>
Date: 2018-03-15 09:27:42

Hi Balbir,

On Thu, 15 Mar 2018 19:42:33 +1100 Balbir Singh [off-list ref] wrote:
On Wed, Mar 14, 2018 at 4:23 PM, Stephen Rothwell [off-list ref] wrote:
quoted
I also get these from a powerpc allyesconfig build of linux-next:

WARNING: vmlinux.o(.text+0x7c81c): Section mismatch in reference from the function .stop_machine_change_mapping() to the function .meminit.text:.create_physical_mapping()
The function .stop_machine_change_mapping() references
the function __meminit .create_physical_mapping().
This is often because .stop_machine_change_mapping lacks a __meminit
annotation or the annotation of .create_physical_mapping is wrong.

WARNING: vmlinux.o(.text+0x7c828): Section mismatch in reference from the function .stop_machine_change_mapping() to the function .meminit.text:.create_physical_mapping()
The function .stop_machine_change_mapping() references
the function __meminit .create_physical_mapping().
This is often because .stop_machine_change_mapping lacks a __meminit
annotation or the annotation of .create_physical_mapping is wrong.
 
Patches have been sent to fix this - http://patchwork.ozlabs.org/patch/883991/
Excellent, thanks.

-- 
Cheers,
Stephen Rothwell
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help