On 10/21/2014 04:56 PM, Stephen Boyd wrote:
> On 10/21/2014 04:35 PM, j...@joshtriplett.org wrote:
>> --->8---
>> From 1646d051a4a4c18b9a6163fceabcafa20628c728 Mon Sep 17 00:00:00 2001
>> From: Josh Triplett
>> Date: Tue, 21 Oct 2014 16:14:19 -0700
>> Subject: [PATCH] linux/init.h: Always omit __e
On 10/21/2014 04:35 PM, j...@joshtriplett.org wrote:
> On Tue, Oct 21, 2014 at 11:19:01PM +0200, Peter Hüwe wrote:
>> as far as I remember everything marked with __exit or __exit_data will only
>> be
>> used/called when unloading a module, and gets moved to the .exit.text or
>> .exit.data sectio
On Tue, Oct 21, 2014 at 11:19:01PM +0200, Peter Hüwe wrote:
> as far as I remember everything marked with __exit or __exit_data will only
> be
> used/called when unloading a module, and gets moved to the .exit.text or
> .exit.data sections.
>
> Why are these sections present in the vmlinux/vmli
Hi,
as far as I remember everything marked with __exit or __exit_data will only be
used/called when unloading a module, and gets moved to the .exit.text or
.exit.data sections.
Why are these sections present in the vmlinux/vmlinux.bin/bzImage and not
dropped by the linker or at least objdump?
4 matches
Mail list logo