Gitweb:     
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1499993cc7bfd568f471bd697499cff394e46822
Commit:     1499993cc7bfd568f471bd697499cff394e46822
Parent:     5409bae07a63630ba5a40f3f00b7f3e6d7eceedd
Author:     Sam Ravnborg <[EMAIL PROTECTED]>
AuthorDate: Wed Feb 28 20:12:31 2007 -0800
Committer:  Linus Torvalds <[EMAIL PROTECTED]>
CommitDate: Thu Mar 1 14:53:37 2007 -0800

    [PATCH] fix section mismatch warning in lockdep
    
    lockdep_init() is marked __init but used in several places
    outside __init code. This causes following warnings:
    $ scripts/mod/modpost kernel/lockdep.o
    WARNING: kernel/built-in.o - Section mismatch: reference to 
.init.text:lockdep_init from .text.lockdep_init_map after 'lockdep_init_map' 
(at offset 0x105)
    WARNING: kernel/built-in.o - Section mismatch: reference to 
.init.text:lockdep_init from .text.lockdep_reset_lock after 
'lockdep_reset_lock' (at offset 0x35)
    WARNING: kernel/built-in.o - Section mismatch: reference to 
.init.text:lockdep_init from .text.__lock_acquire after '__lock_acquire' (at 
offset 0xb2)
    
    The warnings are less obviously due to heavy inlining by gcc - this is not
    altered.
    
    Fix the section mismatch warnings by removing the __init marking, which
    seems obviously wrong.
    
    Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]>
    Acked-by: Ingo Molnar <[EMAIL PROTECTED]>
    Cc: <[EMAIL PROTECTED]>
    Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
    Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
---
 kernel/lockdep.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/kernel/lockdep.c b/kernel/lockdep.c
index a08a172..8dc24c9 100644
--- a/kernel/lockdep.c
+++ b/kernel/lockdep.c
@@ -2602,7 +2602,7 @@ out_restore:
        raw_local_irq_restore(flags);
 }
 
-void __init lockdep_init(void)
+void lockdep_init(void)
 {
        int i;
 
-
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to