Comment # 10 on bug 1177403 from Mel Gorman

(In reply to Michal Suchanek from comment #9)
> It is non-trivial to make use of the warnings. There are others that we can
> make use of but don't currently.
> 

I'm reading that as the "information is not used"

> It would help to know what they look like, too.
> 

Random example

WARNING: vmlinux.o(.text+0x8c68): Section mismatch in reference from the
variable start_here_common to the function .init.text:start_kernel()
The function start_here_common() references
the function __init start_kernel().
This is often because start_here_common lacks a __init
annotation or the annotation of start_kernel is wrong.

Mostly these are useful during development time only when adding code that uses
__init annotation. This can come up during development when adding code related
to hotplug which accidentally calls __init functions at runtime when the __init
code has already been freed in the latter parts of boot.

> However, I see enabling them in kbuild as low priority.

So are you ok if I disable them? It's an option that should be set only during
development time, in production, it's useless and as the original summaries
states, it affects what functions get inlined.