![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1177403 https://bugzilla.suse.com/show_bug.cgi?id=1177403#c3 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msuchanek@suse.com Flags| |needinfo?(msuchanek@suse.co | |m) --- Comment #3 from Jiri Slaby <jslaby@suse.com> --- (In reply to Jiri Slaby from comment #1)
One more note: I would personally disable the option in all flavours except -debug.
(In reply to Mel Gorman from comment #2)
The real qusetion is -- why enable this at all for a production build? It would make more sense to build with this option when considering whether a branch should be merged or not and mail when new warnings are added due to section mismatches.
Or this, sure. Michal, could DEBUG_SECTION_MISMATCH be set to y during build tests, please? Then I would disable it in all our maintained non-ltss configs. -- You are receiving this mail because: You are on the CC list for the bug.