---

yaml
---
r: 213551
b: refs/heads/master
c: 5ea0817
h: refs/heads/master
i:
  213549: 19284df
  213547: 2116cf1
  213543: 55be852
  213535: 3b4327d
v: v3

[refs]

@@ -1,2 +1,2 @@
 ---
-refs/heads/master: c9bfff9c98671ad50e4abbfe1ab606a9957f7539
+refs/heads/master: 5ea081785dde6041eb2f4acc2369abbb9099a981

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)