linux-kernel - [PATCH] resource.c: Fixing 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>] [thread-next>] [day] [month] [year] [list]

Message-ID: <b9df5fa10810292035p4c5a70eay44efae337a38d067@mail.gmail.com>
Date:	Thu, 30 Oct 2008 09:35:24 +0600
From:	"Rakib Mullick" <rakib.mullick@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	"Ingo Molnar" <mingo@...e.hu>,
	"Andrew Morton" <akpm@...ux-foundation.org>
Subject: [PATCH] resource.c: Fixing section mismatch warning .

 LD      kernel/built-in.o
WARNING: kernel/built-in.o(.text+0xfcad): Section mismatch in
reference from the function reserve_region_with_split() to the
function .init.text:__reserve_region_with_split()
The function reserve_region_with_split() references
the function __init __reserve_region_with_split().
This is often because reserve_region_with_split lacks a __init
annotation or the annotation of __reserve_region_with_split is wrong.

This patch fixes the above warning.

Thanks.

Signed-off-by: Md.Rakib H. Mullick <rakib.mullick@...il.com>

--- linux-2.6-orig/kernel/resource.c	2008-10-28 20:52:38.000000000 +0600
+++ linux-2.6/kernel/resource.c	2008-10-28 22:34:44.000000000 +0600
@@ -571,7 +571,7 @@ static void __init __reserve_region_with

 }

-void reserve_region_with_split(struct resource *root,
+void __init reserve_region_with_split(struct resource *root,
 		resource_size_t start, resource_size_t end,
 		const char *name)
 {
--
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/