linux-kernel - [PATCH] kvmclock.c: Fix section mismatch warning.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <b9df5fa10810171917n31fc38a4j4805a38df2e83f51@mail.gmail.com>
Date:	Sat, 18 Oct 2008 08:17:58 +0600
From:	"Rakib Mullick" <rakib.mullick@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Ingo Molnar" <mingo@...e.hu>
Subject: [PATCH] kvmclock.c: Fix section mismatch warning.

WARNING: arch/x86/kernel/built-in.o(.text+0x1722c): Section mismatch
in reference from the function kvm_setup_secondary_clock() to the
function .devinit.text:setup_secondary_APIC_clock()
The function kvm_setup_secondary_clock() references
the function __devinit setup_secondary_APIC_clock().
This is often because kvm_setup_secondary_clock lacks a __devinit
annotation or the annotation of setup_secondary_APIC_clock is wrong.

This patch fixes the above warning.
Thanks.

Signed-off-by: Md.Rakib H. Mullick(rakib.mullick@...il.com)

--- linux-2.6-orig/arch/x86/kernel/kvmclock.c	2008-10-16
20:03:12.000000000 +0600
+++ linux-2.6/arch/x86/kernel/kvmclock.c	2008-10-17 23:48:54.000000000 +0600
@@ -100,7 +100,7 @@ static int kvm_register_clock(char *txt)
 }

 #ifdef CONFIG_X86_LOCAL_APIC
-static void kvm_setup_secondary_clock(void)
+static void __devinit kvm_setup_secondary_clock(void)
 {
 	/*
 	 * Now that the first cpu already had this clocksource initialized,
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/