CCing stable, as this patch didn't make it in v3.9.
Mainline commit ID is 22ee3b57c3ff71772b0c4178404b04f5df78d501.
On Wed, Apr 24, 2013 at 11:40 AM, Geert Uytterhoeven
wrote:
> If gcc (e.g. 4.1.2) decides not to inline vsock_init_tables(), this will
> cause a section mismatch:
>
> WARNING:
CCing stable, as this patch didn't make it in v3.9.
Mainline commit ID is 22ee3b57c3ff71772b0c4178404b04f5df78d501.
On Wed, Apr 24, 2013 at 11:40 AM, Geert Uytterhoeven
ge...@linux-m68k.org wrote:
If gcc (e.g. 4.1.2) decides not to inline vsock_init_tables(), this will
cause a section mismatch:
From: Geert Uytterhoeven
Date: Wed, 24 Apr 2013 11:40:55 +0200
> If gcc (e.g. 4.1.2) decides not to inline vsock_init_tables(), this will
> cause a section mismatch:
>
> WARNING: net/vmw_vsock/vsock.o(.text+0x1bc): Section mismatch in reference
> from the function __vsock_core_init() to the
From: Geert Uytterhoeven ge...@linux-m68k.org
Date: Wed, 24 Apr 2013 11:40:55 +0200
If gcc (e.g. 4.1.2) decides not to inline vsock_init_tables(), this will
cause a section mismatch:
WARNING: net/vmw_vsock/vsock.o(.text+0x1bc): Section mismatch in reference
from the function
If gcc (e.g. 4.1.2) decides not to inline vsock_init_tables(), this will
cause a section mismatch:
WARNING: net/vmw_vsock/vsock.o(.text+0x1bc): Section mismatch in reference from
the function __vsock_core_init() to the function .init.text:vsock_init_tables()
The function __vsock_core_init()
If gcc (e.g. 4.1.2) decides not to inline vsock_init_tables(), this will
cause a section mismatch:
WARNING: net/vmw_vsock/vsock.o(.text+0x1bc): Section mismatch in reference from
the function __vsock_core_init() to the function .init.text:vsock_init_tables()
The function __vsock_core_init()
6 matches
Mail list logo