I'm seeing the following warning:
WARNING: vmlinux.o(.init.text+0x1acdc): Section mismatch: reference to
.exit.text:gfar_mdio_exit (between 'gfar_init' and 'gfar_mdio_init')
I don't understand why its not ok to access .exit.text from .init.text
The following addresses the issue, however I don't
On Wed, Jul 25, 2007 at 02:14:12AM -0500, Kumar Gala wrote:
I'm seeing the following warning:
WARNING: vmlinux.o(.init.text+0x1acdc): Section mismatch: reference to
.exit.text:gfar_mdio_exit (between 'gfar_init' and 'gfar_mdio_init')
I don't understand why its not ok to access .exit.text
On Jul 25, 2007, at 2:27 AM, Sam Ravnborg wrote:
On Wed, Jul 25, 2007 at 02:14:12AM -0500, Kumar Gala wrote:
I'm seeing the following warning:
WARNING: vmlinux.o(.init.text+0x1acdc): Section mismatch:
reference to
.exit.text:gfar_mdio_exit (between 'gfar_init' and 'gfar_mdio_init')
I
For the popular architectures (i386,x86_64) we discard .exit.text at
runtime so here we do not see the error from ld (sadly).
Fair point, wondering what we do with .exit on PPC, another thing for
the list :)
from:
arch/ppc/kernel/vmlinux.lds.S:
/* .exit.text is discarded at runtime,
On Wed, 2007-07-25 at 02:14 -0500, Kumar Gala wrote:
I'm seeing the following warning:
WARNING: vmlinux.o(.init.text+0x1acdc): Section mismatch: reference to
.exit.text:gfar_mdio_exit (between 'gfar_init' and 'gfar_mdio_init')
I don't understand why its not ok to access .exit.text from
On Wed, 2007-07-25 at 09:27 +0200, Sam Ravnborg wrote:
On Wed, Jul 25, 2007 at 02:14:12AM -0500, Kumar Gala wrote:
I'm seeing the following warning:
WARNING: vmlinux.o(.init.text+0x1acdc): Section mismatch: reference to
.exit.text:gfar_mdio_exit (between 'gfar_init' and 'gfar_mdio_init')
On Wed, Jul 25, 2007 at 06:08:03PM +0800, chengong wrote:
On Wed, 2007-07-25 at 09:27 +0200, Sam Ravnborg wrote:
On Wed, Jul 25, 2007 at 02:14:12AM -0500, Kumar Gala wrote:
I'm seeing the following warning:
WARNING: vmlinux.o(.init.text+0x1acdc): Section mismatch: reference to
