From 7aff6345e8dc745d0f7140bc904da22e1b9df2cc Mon Sep 17 00:00:00 2001 From: Michal Nazarewicz Date: Thu, 12 Aug 2010 17:43:56 +0200 Subject: [PATCH] --- yaml --- r: 213551 b: refs/heads/master c: 5ea081785dde6041eb2f4acc2369abbb9099a981 h: refs/heads/master i: 213549: 19284dff5c02929b3d93219728286c094f511678 213547: 2116cf14160fadd8689f8fb6f6a7ad2a64c36e06 213543: 55be852828b457b54d5e6349a42948cd793ce756 213535: 3b4327d13a8e5eb665e71df3b513ee060ce44e42 v: v3 --- [refs] | 2 +- trunk/include/linux/init.h | 13 ++++++++++--- 2 files changed, 11 insertions(+), 4 deletions(-) diff --git a/[refs] b/[refs] index a5ac57539730..a1c8684f7eca 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: c9bfff9c98671ad50e4abbfe1ab606a9957f7539 +refs/heads/master: 5ea081785dde6041eb2f4acc2369abbb9099a981 diff --git a/trunk/include/linux/init.h b/trunk/include/linux/init.h index de994304e0bb..577671c55153 100644 --- a/trunk/include/linux/init.h +++ b/trunk/include/linux/init.h @@ -46,16 +46,23 @@ #define __exitdata __section(.exit.data) #define __exit_call __used __section(.exitcall.exit) -/* modpost check for section mismatches during the kernel build. +/* + * modpost check for section mismatches during the kernel build. * A section mismatch happens when there are references from a * code or data section to an init section (both code or data). * The init sections are (for most archs) discarded by the kernel * when early init has completed so all such references are potential bugs. * For exit sections the same issue exists. + * * The following markers are used for the cases where the reference to * the *init / *exit section (code or data) is valid and will teach - * modpost not to issue a warning. - * The markers follow same syntax rules as __init / __initdata. */ + * modpost not to issue a warning. Intended semantics is that a code or + * data tagged __ref* can reference code or data from init section without + * producing a warning (of course, no warning does not mean code is + * correct, so optimally document why the __ref is needed and why it's OK). + * + * The markers follow same syntax rules as __init / __initdata. + */ #define __ref __section(.ref.text) noinline #define __refdata __section(.ref.data) #define __refconst __section(.ref.rodata)